cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

databricks all-purpose cluster

Ved88
New Contributor II

getting below error-Failure starting repl. Try detaching and re-attaching the notebook. while executing notebook and can see cluster have all installed lib.

4 REPLIES 4

Ved88
New Contributor II

Ved88_0-1767782518406.png

i can see metastore is down ,is that the reason notebook is not executing

NandiniN
Databricks Employee
Databricks Employee

Hi @Ved88 , 

Usually this error occurs in case of library issues or conflict with versions. If you remove the libraries, do you still see the issue.

Additionally, review the driver logs to see if you see metastore related logs, which can give insights on what is the issue with the metastore.

Thanks!

Ved88
New Contributor II

Hi ,

this issue might be related to hive metastore migration related.PFB

i can see driver log having this connection issue which matching the host in below url-IP CIDR For Azure Databricks Hive Metastore - Databricks Community - 133401

Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to address=(host=consolidated-westeuropec2-prod-metastore-0.mysql.database.azure.com)(port=3306)(type=master) : Socket fail to connect to host:consolidated-westeuropec2-prod-metastore-0.mysql.database.azure.com, port:3306. Connection refused

 

please share the steps to overcome this hive migration IP.

thanks!

Ved

 

 

 

nayan_wylde
Esteemed Contributor

SQLNonTransientConnectionException with port 3306 strongly points to egress being blocked from your Databricks compute to the default Hive Metastore (which runs on Azure Database for MySQL). Databricks recently published the reserved IP ranges and guidance for allowlisting the metastore endpoints; if your firewall / UDRs still have the old IPs or only allow specific ranges, youโ€™ll see exactly this error.

https://community.databricks.com/t5/product-platform-updates/ip-cidr-for-azure-databricks-hive-metas...