Azure Databricks, notebook not running

Question

I created a new databricks cluster, it is running fine. I am trying to run simple python commands like
"import time" in my databricks notebook on the respective cluster. It won't run, seems like a configuration issue. Please help on resolving it. It is giving the following error:

Error: Failure starting repl. Try detaching and re-attaching the notebook.

java.lang.Exception: org.apache.hadoop.hive.ql.metadata.HiveException: java.lang.RuntimeException: Unable to instantiate org.apache.hadoop.hive.metastore.HiveMetaStoreClient   at org.apache.spark.sql.hive.HiveExternalCatalog.$anonfun$withClient$2(HiveExternalCatalog.scala:160)   at org.apache.spark.sql.hive.HiveExternalCatalog.maybeSynchronized(HiveExternalCatalog.scala:112)   at org.apache.spark.sql.hive.HiveExternalCatalog.$anonfun$withClient$1(HiveExternalCatalog.scala:150)   at com.databricks.backend.daemon.driver.ProgressReporter$.withStatusCode(ProgressReporter.scala:364)   at com.databricks.spark.util.SparkDatabricksProgressReporter$.withStatusCode(ProgressReporter.scala:34)   at org.apache.spark.sql.hive.HiveExternalCatalog.withClient(HiveExternalCatalog.scala:149)   at org.apache.spark.sql.hive.HiveExternalCatalog.databaseExists(HiveExternalCatalog.scala:300)   at org.apache.spark.sql.internal.SharedState.externalCatalog$lzycompute(SharedState.scala:220)   at org.apache.spark.sql.internal.SharedState.externalCatalog(SharedState.scala:211)   at org.apache.spark.sql.hive.HiveSessionStateBuilder.externalCatalog(HiveSessionStateBuilder.scala:59)   at org.apache.spark.sql.hive.HiveSessionStateBuilder.$anonfun$resourceLoader$1(HiveSessionStateBuilder.scala:66)   at org.apache.spark.sql.hive.HiveSessionResourceLoader.client$lzycompute(HiveSessionStateBuilder.scala:162)

Answer 1

@Samadipa Saha Welcome to Microsoft Q&A forum and thanks for reaching out here.

As of now I don't know what your cluster configuration was. But as per my research based on the error message your provided, most of the time this issue occurs due to Library conflicts. please check your library and try to clone that cluster then run.

Below are couple of forum threads where a similar issue has been discussed along with root cause and resolution. Kindly go through them.

1. Databricks community forum thread - Failure starting repl
2. Databricks stackoverflow thread - Failure Starting REPL

Hope this info helps. Do let us know how it goes.

---

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.