This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I'm trying to create a container with dedicated throughput, but I'm facing the following Error:
Error while creating container defects:
Service is currently unavailable. More info: https://aka.ms/cosmosdb-tsg-service-unavailable
ActivityId: 6d8b6e57-0d2c-402b-9325-f7995e29097d, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0
ActivityId: 09cdb6e8-381a-466c-ab78-585181005332, Microsoft.Azure.Documents.Common/2.14.0
Container:
Database:
Server:
My database throughput limit is 2000 RU, and my cosmos throughput is unlimited, so I guess the issue is not because of my limits.
Do you have any idea how I can resolve this issue?
Thanks
Hi, @Mahdi Welcome to the Microsoft Q&A forum, Thanks for posting your question.
As I understand you are trying to create a container with dedicated throughput and facing the issue. I am trying to reproduce the issue and will provide you with more details.
Regards
Geetha
Hi @GeethaThatipatri-MSFT
thanks for your response. I test it in another cosmos DB, and it works there too. The problem with dropping the database is this is one of our production DBs.
Moreover, I tried to create a new database with dedicated throughput, but again I received the same error (this time for the database instead of data collection/container), so I guess there is an issue with my cosmos DB account.
Is there any way I can have more details about this error to trace the issue? I would love to avoid migrating the whole DB to a new Cosmos DB.
Thanks
Hi @Mahdi I tried in my environment and I don't see any issues, it could be an intermittent issue can you delete and retry one more time
Here is the screenshot from my side
Regards
Geetha
Solution:
The problem was the cosmos RU capacity at the zone we built in our cosmos DB.
MS added more cosmos capacity to the ZONE (Germany West Central), and the problem is solved!
If you face the same issue, please contact Microsoft support.
Special thanks to @GeethaThatipatri-MSFT for the tremendous support!
Thanks
@Mahdi Thank you for visiting the Microsoft QA forums! Have a great day!