How to retrieve the usage details of CosmosDB for adjusting the throughput

In common scenarios, if a server happens to meet short-time high loads, Azure CosmosDB will response with 429 status code. If you are using Azure CosmosDB SDK, the SDK will get the waiting time from the header and will implicitly retry the former request. However, if the server is just meeting long-time high loads or there are several clients, exceptions might be thrown out. At the time, we can catch this exception and scale up the throughput to a higher level to handle the long-time high loads. For how to adjust the throughput, you can refer to: Modifying the throughput of the Azure... Read more

Modifying the throughput of the Azure Cosmos DB container through the Java SDK

When using Azure Cosmosdb, when you enable a new collection, table, or graphic, you specify the number of requests per second (RU) that you want to keep.Azure Cosmos DB allocates physical partitions according to the throughput of the allocation, and splits/balances the growing data in the partition. Because the user needs to pay according to the reserved throughput, no matter how much throughput is actually used.As the application’s load, data, and usage patterns change, the actual throughput may vary, so many users want to be able to modify the throughput.The current Azure portal offers modified options, as well as programmatic... Read more