Unity Catalog metastore is down error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2023 10:31 AM - edited 07-25-2023 11:11 AM
When I want to run notebook in databricks all queries, saves and read take really long and I found error message in the clusters event log that says: Metastore is down. So, I think cluster is not able to connect to the metastore right now. Could be this the reason? I tried to create another cluster but with the same result. Any help on this? Unity catalog`s Metastore is on ADLS gen2. and we use premium workspace.
After few minutes the command is finished. But simple load of delta table with few records takes 5 minutes or so.
Thanks
- Labels:
-
Delta Lake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2023 11:34 PM
Hi Kaniz. Thanks for reply. Just want to add some information. Im not sure if this error message is related to legacy Hive metastore or to Unity Catalog. We use UC from the beginning. Our metastore is on external storage - see screenshot.
This error occurs in the clusters event log exactly 6 minutes after the start of the cluster. Every time we start the cluster that error is there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 09:43 AM
@alesventus what is size of your data and what type of cluster size you are using. also is your workspace region and metastore region same
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2024 08:42 AM
@alesventus I think "Metastore is down" here is related to the legacy Hive metastore. You can find the stack trace in the driver logs.
In your case do you need Hivemetastore?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2024 12:04 AM
This issue is solely related to the VNET. Azure engineer must set up connection within VNET correctly.

