Cosmos DB emulator returns ServiceUnavailable (503)

Question

Cosmos DB emulator returns ServiceUnavailable (503)

Renze Yu 47 Microsoft Employee

We meet error from Cosmos DB emulator "Response status code does not indicate success: ServiceUnavailable (503)" on Windows. This seems to be related with how fast we call it.

Our user scenario is in unit test. We connect our unit test to Cosmos DB emulator instead of real Azure Cosmos DB. The first step is to read bunch of files from JSON files, and set up database, containers, and items.

We find some calls will fail when creating them with error 503, which fails the later unit tests that relies on these data. The error only happens where preparing the data, so we suspect there is some capacity limit within it, but we cannot identify the root cause with the limited error message.

I see some similar issues reported in GitHub (e.g. https://github.com/Azure/azure-cosmos-dotnet-v2/issues/817), but cannot find a solution to it.

SSingh-MSFT 16,371 Reputation points Moderator

2023-10-18T08:43:22.73+00:00

Hi
Renze Yu •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Thanks
Renze Yu 47 Reputation points Microsoft Employee

2023-10-18T08:49:33.8133333+00:00
Thanks for your answer. We are testing these options. Will report back when it is resolved.

At the same time, we think it may be related to the count of containers created, so we are reducing the count. The below document mentions these restrictions:

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator#differences-between-the-emulator-and-cloud-service

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator-windows-arguments#change-the-number-of-default-containers
SSingh-MSFT 16,371 Reputation points Moderator

2023-10-25T05:15:27.9433333+00:00

Hi
Renze Yu •,

Following up to see if the below suggestion was helpful. If this answers your query, do click Accept Answer and Mark Helpful for the same. And, if you have any further query do let us know. Thanks

Accepted answer

0 additional answers

Your answer

SSingh-MSFT 16,371 Reputation points Moderator

2023-10-18T08:43:22.73+00:00

Hi
Renze Yu •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Thanks
Renze Yu 47 Reputation points Microsoft Employee

2023-10-18T08:49:33.8133333+00:00

Thanks for your answer. We are testing these options. Will report back when it is resolved.

At the same time, we think it may be related to the count of containers created, so we are reducing the count. The below document mentions these restrictions:

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator#differences-between-the-emulator-and-cloud-service

https://learn.microsoft.com/en-us/azure/cosmos-db/emulator-windows-arguments#change-the-number-of-default-containers
SSingh-MSFT 16,371 Reputation points Moderator

2023-10-25T05:15:27.9433333+00:00

Hi
Renze Yu •,

Following up to see if the below suggestion was helpful. If this answers your query, do click Accept Answer and Mark Helpful for the same. And, if you have any further query do let us know. Thanks

Answer 1

Hi
Renze Yu •,

Welcome to Microsoft Q&A forum.

As I understand, your Cosmos DB emulator returns ServiceUnavailable (503).

Could you please try below:

1). Try resetting data which will clean containers and database.

2). Try increasing the emulator capacity.

Use:

First through the AZURE_COSMOS_EMULATOR_PARTITION_COUNT environment variable (here an extract on our docker compose):

cosmos_db_service:

container_name: cosmos_db

image: mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest

environment:

AZURE_COSMOS_EMULATOR_PARTITION_COUNT=20
AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=true

AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=127.0.0.1

Second by defining a higher offerThroughput for each container (defined during our schema provisioning process):

await client.database(env.vars.MICROSOFT_COSMOSDB_DATABASE).containers.createIfNotExists(

{ id: containerId },

{ offerThroughput: 10000 } // throughput values between 400 and 1000000 inclusive in increments of 100

)

Please try and let us know the result. Thank you.

Share via

Cosmos DB emulator returns ServiceUnavailable (503)

0 additional answers

Your answer