DP-420 · Question #191
You have an Azure Cosmos DB for NoSQL container named Contained that has a provisioned throughput of 1,000 request units per second (RU/s). Contained is queried by using an app named App1. Users of…
The correct answer is D. Increase the provisioned throughout of Container1. E. Add retry logic to App1. Diagnose and troubleshoot Azure Cosmos DB request rate too large (429) exceptions There are different error messages that correspond to different types of 429 exceptions: (D) -> Request rate is large. More Request Units may be needed, so no changes were made. The request didn't…
Question
You have an Azure Cosmos DB for NoSQL container named Contained that has a provisioned throughput of 1,000 request units per second (RU/s). Contained is queried by using an app named App1. Users of App1 report that several times a day, they receive the following error message: “HTTP error code 429” You need to improve the reliability of App1 without affecting the performance of the app. What are two ways to improve the reliability? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Options
- AAdd a trigger to Container1.
- BUpdate App1 to split large requests into several smaller requests.
- CUpdate App1 to reduce the size of each request to less than 1 MB.
- DIncrease the provisioned throughout of Container1.
- EAdd retry logic to App1.
How the community answered
(30 responses)- A7% (2)
- B7% (2)
- C13% (4)
- D73% (22)
Explanation
Diagnose and troubleshoot Azure Cosmos DB request rate too large (429) exceptions There are different error messages that correspond to different types of 429 exceptions: (D) *-> Request rate is large. More Request Units may be needed, so no changes were made. The request didn't complete due to a high rate of metadata requests. *-> The request didn't complete due to a transient service error. (E) Rate limiting due to transient service error This 429 error is returned when the request encounters a transient service error. Increasing the RU/s on the database or container will have no impact and isn't recommended. Recommended solution Retry the request. If the error persists for several minutes, file a support ticket from the Azure Note: A "Request rate too large" exception, also known as error code 429, indicates that your requests against Azure Cosmos DB are being rate limited. When you use provisioned throughput, you set the throughput measured in request units per second (RU/s) required for your workload. Database operations against the service such as reads, writes, and queries consume some number of request units (RUs). In a given second, if the operations consume more than the provisioned request units, Azure Cosmos DB will return a 429 exception. Each second, the number of request units available to There are different error messages that correspond to different types of 429 exceptions: (D) *-> Request rate is large. More Request Units may be needed, so no changes were made. The request didn't complete due to a high rate of metadata requests. (E) *-> The request didn't complete due to a transient service error. https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/troubleshoot-request-rate-too-large
Topics
Community Discussion
No community discussion yet for this question.