-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[core] Retry on 503 using the Retry-After header #15906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
7885d61
8ab4e31
13a7ff9
0cc46d2
efef18f
da64440
a2685f6
74bbb41
fdd9ecf
b561d19
33260ec
502f682
0127649
023ce55
8b7fa25
3539c30
a6636a1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| // Copyright (c) Microsoft Corporation. | ||
| // Licensed under the MIT license. | ||
|
|
||
| /** | ||
| * Maximum number of retries for the throttling retry policy | ||
| */ | ||
| export const DEFAULT_CLIENT_MAX_RETRY_COUNT = 3; | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don’t believe we should preemptively expose this to the public API. If anything, now we retry up to 3 times on the throttlingRetryPolicy, while we were only retrying one time before.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Three is good, and is the same default value for exponential and system error retry policy. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I decided to put this in a separate conditional to make it easier to think through.