cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Bangalore
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Not able to create a unity metastore in a specified region

RC
Contributor

Hi Team,

I'm not able to create a metastore in a region (us-east-1).

It tells me that "This region already contains a metastore. Only a single metastore is allowed per region"

But we don't have any metastore. Earlier we had one metastore we had deleted it. Now we are not able to recreate it again. Is there any other place dbr saves the metadata of the metastore?

1 ACCEPTED SOLUTION

Accepted Solutions

RC
Contributor

@here - there were dangling resources under storage credentials and storage credentials. Had to delete everything

View solution in original post

3 REPLIES 3

Anonymous
Not applicable

@Rajath Cโ€‹ :

It's possible that the metadata of the previously deleted metastore is still being cached somewhere, which is causing the issue.

You can try the following steps to troubleshoot the issue:

  1. Check if there are any lingering resources from the previously deleted metastore, such as an S3 bucket or a Glue catalog. If so, delete them.
  2. Try creating the metastore in a different region and see if it works. If it does, then it confirms that the issue is specific to the us-east-1 region.
  3. If none of the above steps work, contact Databricks support for further assistance. They should be able to help you identify the root cause of the issue and provide a solution.

Anonymous
Not applicable

Hi @Rajath Cโ€‹ 

Thank you for posting your question in our community! We are happy to assist you.

To help us provide you with the most accurate information, could you please take a moment to review the responses and select the one that best answers your question?

This will also help other community members who may have similar questions in the future.

Thank you for your participation and let us know if you need any further assistance! 

RC
Contributor

@here - there were dangling resources under storage credentials and storage credentials. Had to delete everything

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.