Update troubleshoot-request-rate-too-large.md #295
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"10,0000" has one zero too much. It should should "10,000" instead. This also matches the calculation that are done later throughout the article
|
@jraufeisen : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
azure-cosmos-db/svc
Change sent to author
nosql/subsvc
labels
|
Learn Build status updates of commit 05affa6: ✅ Validation status: passed
For more details, please refer to the build report. |
markjbrown
approved these changes
Jul 19, 2025
|
#sign-off |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the article Diagnose and troubleshoot Azure Cosmos DB request rate too large (429) exceptions, there's a small typo regarding maximum throughput of a CosmosDB container
"10,0000" has one zero too many. It should be "10,000" instead (= 10k). This also matches the calculation that are done later throughout the article