chore(AIP-4221): change example retry policy values#1519
Merged
noahdietz merged 2 commits intoaip-dev:masterfrom Jul 8, 2025
Merged
chore(AIP-4221): change example retry policy values#1519noahdietz merged 2 commits intoaip-dev:masterfrom
noahdietz merged 2 commits intoaip-dev:masterfrom
Conversation
The original Google API Design Guide recommended 1s initial delay, which is more sensible than 0.01s. Azure recommends 5s. 2 is the most popular delay multiplier in the industry. As an example, we should use the most popular choice. 60s timeout often leads to thread exhaustion and user frustration and server overloading. Historically, all Google APIs use either 5s or 10s as the deadline. This is especially true for Google REST client libraries.
noahdietz
changed the title
noahdietz
approved these changes
Jul 7, 2025
Collaborator
noahdietz
left a comment
noahdietz
left a comment
There was a problem hiding this comment.
These values were never intended to be used as guiding examples and this AIP isn't even relevant to API producers - it's a client library AIP with an example of the configuration they'd expect.
That said, the example can be updated.
I'll Approve but leave @jskeet to +2
jskeet
approved these changes
Jul 8, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The original Google API Design Guide recommended 1s initial delay, which is more sensible than 0.01s. Azure recommends 5s.
2x is the most popular delay multiplier in the industry. As an example, we should use the most popular choice.
60s timeout often leads to thread exhaustion and user frustration and server overloading. Historically, all Google APIs use either 5s or 10s as the deadline. This is especially true for Google REST client libraries.