Why am i not allowed to create a container in my Cosmos Emulator database ? i have this error: Sorry, we are currently experiencing high demand in this region South Central US, and cannot fulfill your request at this time Wed, 02 Apr 2025 01:10:27 GMT.

Question

Why am i not allowed to create a container in my Cosmos Emulator database ? i have this error: Sorry, we are currently experiencing high demand in this region South Central US, and cannot fulfill your request at this time Wed, 02 Apr 2025 01:10:27 GMT.

stephanely 0

Create a container on my database in Cosmos DB emulator

Sorry, we are currently experiencing high demand in this region South Central US, and cannot fulfill your request at this time Wed, 02 Apr 2025 01:10:27 GMT. ActivityId: e567eaff-bb3e-4c5a-9f65-1fb99af10b41, Microsoft.Azure.Documents.Common/2.14.0

Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-02T02:26:37+00:00

Hi stephanely,Greetings!

As the error message mentions this issue is related to high demand in South Central US region, could you please try to create it once again and if fails please try with other regions. Some regions face capacity issue due to high demand.
stephanely 0 Reputation points

2025-04-02T02:52:25.6866667+00:00

Hi Prasad, I think I am encountering this issue: https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/78
After testing, I see that I can't add a 13th container to my database.

I have tried the solution proposed in the discussion, add /PartitionCount=60 when starting the emulator but it has not solved my issue.
To give more context, it's a Windows VM.
Any idea to fix this ?
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-02T04:50:47.4266667+00:00
Hi stephanely,

Sorry for the inconvience, I am understanding that hitting a limit with the Azure Cosmos DB Emulator. Here are a few additional steps you can try:

Increase Partition Count Further:

You mentioned trying /PartitionCount=60. You might need to increase this even further. Try setting it to a higher value, such as 100:

CosmosDB.Emulator.exe /PartitionCount=100

Ensure that you are using the latest version of the Cosmos DB Emulator. Sometimes, newer versions have optimizations and bug fixes that might help with your issue. You can download the latest version from the

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator

Make sure your VM has enough resources (CPU, memory) allocated. Increasing the VM size might help if it's running low on resources.

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-03T04:13:32.43+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
stephanely 0 Reputation points

2025-04-03T04:45:15.6033333+00:00

Hi Prasad, sorry I forgot to reply, I tried your solution, i.e. extending the Partition Count, but it didn't work, and I was already on the latest version of the emulator.

The issue is on a build VM I use to run the CI build with integration tests using cosmos db emulator. I'll try to see if upgrading the specs will help.
As a stopgap, I have created a cosmos db account so that I can run the CI build again, but it's not ideal.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-03T08:12:13.6266667+00:00
Hi stephanely,

you are facing a challenging issue with the Azure Cosmos DB Emulator on your build VM. Here are a few more steps that might help:

1.Optimize VM Resources:

Ensure your build VM has sufficient CPU and memory. Sometimes, increasing the VM size can help with performance and resource allocation.

2.Use Docker for Emulator:

Running the Cosmos DB Emulator in a Docker container can sometimes provide better isolation and resource management. You can pull the Docker image and run it with the following commands:

docker pull mcr.microsoft.com/cosmosdb/windows/azure-cosmos-emulator docker run -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 mcr.microsoft.com/cosmosdb/windows/azure-cosmos-emulator

3.Reset Emulator Data:

If you haven't already, try resetting the emulator data. This can sometimes resolve issues with container limits:

Open the Azure Cosmos DB Emulator context menu from the system tray.

Select Reset Data.

4.Review Emulator Logs:

Check the emulator logs for any specific errors or warnings that might give more insight into the issue. Logs can be found in the %LOCALAPPDATA%\CosmosDBEmulator directory.

5.Consider Using Azure DevOps:

If you're using Azure DevOps, you can set up a CI/CD pipeline with the Azure Cosmos DB Emulator build task. This can help streamline the process and manage resources more effectively1.

6.Alternative Testing Strategies:

As a temporary measure, you might consider running a subset of your tests locally with the emulator and the full suite in the cloud. This can help balance the load and reduce the strain on the emulator.

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-04T08:10:20.6933333+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-07T08:00:03.43+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-02T02:26:37+00:00

Hi stephanely,Greetings!

As the error message mentions this issue is related to high demand in South Central US region, could you please try to create it once again and if fails please try with other regions. Some regions face capacity issue due to high demand.
stephanely 0 Reputation points

2025-04-02T02:52:25.6866667+00:00

Hi Prasad, I think I am encountering this issue: https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/78
After testing, I see that I can't add a 13th container to my database.

I have tried the solution proposed in the discussion, add /PartitionCount=60 when starting the emulator but it has not solved my issue.
To give more context, it's a Windows VM.
Any idea to fix this ?
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-02T04:50:47.4266667+00:00

Hi stephanely,

Sorry for the inconvience, I am understanding that hitting a limit with the Azure Cosmos DB Emulator. Here are a few additional steps you can try:

Increase Partition Count Further:

You mentioned trying /PartitionCount=60. You might need to increase this even further. Try setting it to a higher value, such as 100:

CosmosDB.Emulator.exe /PartitionCount=100

Ensure that you are using the latest version of the Cosmos DB Emulator. Sometimes, newer versions have optimizations and bug fixes that might help with your issue. You can download the latest version from the

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator

Make sure your VM has enough resources (CPU, memory) allocated. Increasing the VM size might help if it's running low on resources.

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-03T04:13:32.43+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
stephanely 0 Reputation points

2025-04-03T04:45:15.6033333+00:00

Hi Prasad, sorry I forgot to reply, I tried your solution, i.e. extending the Partition Count, but it didn't work, and I was already on the latest version of the emulator.

The issue is on a build VM I use to run the CI build with integration tests using cosmos db emulator. I'll try to see if upgrading the specs will help.
As a stopgap, I have created a cosmos db account so that I can run the CI build again, but it's not ideal.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-03T08:12:13.6266667+00:00

Hi stephanely,

you are facing a challenging issue with the Azure Cosmos DB Emulator on your build VM. Here are a few more steps that might help:

1.Optimize VM Resources:

Ensure your build VM has sufficient CPU and memory. Sometimes, increasing the VM size can help with performance and resource allocation.

2.Use Docker for Emulator:

Running the Cosmos DB Emulator in a Docker container can sometimes provide better isolation and resource management. You can pull the Docker image and run it with the following commands:

docker pull mcr.microsoft.com/cosmosdb/windows/azure-cosmos-emulator docker run -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 mcr.microsoft.com/cosmosdb/windows/azure-cosmos-emulator

3.Reset Emulator Data:

If you haven't already, try resetting the emulator data. This can sometimes resolve issues with container limits:

Open the Azure Cosmos DB Emulator context menu from the system tray.

Select Reset Data.

4.Review Emulator Logs:

Check the emulator logs for any specific errors or warnings that might give more insight into the issue. Logs can be found in the %LOCALAPPDATA%\CosmosDBEmulator directory.

5.Consider Using Azure DevOps:

If you're using Azure DevOps, you can set up a CI/CD pipeline with the Azure Cosmos DB Emulator build task. This can help streamline the process and manage resources more effectively1.

6.Alternative Testing Strategies:

As a temporary measure, you might consider running a subset of your tests locally with the emulator and the full suite in the cloud. This can help balance the load and reduce the strain on the emulator.

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-04T08:10:20.6933333+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Prasad Chaganti 410 Reputation points Microsoft External Staff

2025-04-07T08:00:03.43+00:00

Hi stephanely,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Why am i not allowed to create a container in my Cosmos Emulator database ? i have this error: Sorry, we are currently experiencing high demand in this region South Central US, and cannot fulfill your request at this time Wed, 02 Apr 2025 01:10:27 GMT.

Your answer