Status code 449 on read-only workload

Paul Hickman 1 Reputation point
2020-06-03T22:03:47.083+00:00

I am running a batch process using version 3.8 of the .Net core client SDK to access Cosmos DB with an entirely read-only workload; no write operations are occurring on the cosmos account at the time this process is running.

In the metrics reports in Azure Portal, I'm seeing the expected ~25,000/min status code 200 responses to my queries but I'm also seeing around 0 to 2,500/min status code 449 responses. These aren't reaching my code as the .Net client SDK is handling the retry logic so I don't know what queries cause them.

However, according to the documentation status code 449 is only possible for write operations.

Does anyone know why I'm seeing it in my metrics during a read only workload?

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
{count} votes

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.