databricks all-purpose cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
getting below error-Failure starting repl. Try detaching and re-attaching the notebook. while executing notebook and can see cluster have all installed lib.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
i can see metastore is down ,is that the reason notebook is not executing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday - last edited Friday
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
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.