You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a request is found to have failed and to be retried, the applicable HTTP 429 Retry-After or exponential backoff logic kicks in and sleeps for the appropriate amount of time before trying the request again. This sleep occurs even after the last attempt which only delays callers from receiving the ultimate response. Any sleeping should only occur when there is at least one retry attempt remaining.
Combined with #712, this causes any request consistently failing with a retry-able status code to take 90s+ with the default 30s RetryDuration on clients (30s for the first request + 60s for the second request). Made only once and without sleeping after, I see the same request take ~3s.
The text was updated successfully, but these errors were encountered:
Once a request is found to have failed and to be retried, the applicable HTTP 429
Retry-After
or exponential backoff logic kicks in and sleeps for the appropriate amount of time before trying the request again. This sleep occurs even after the last attempt which only delays callers from receiving the ultimate response. Any sleeping should only occur when there is at least one retry attempt remaining.ref:
go-autorest/autorest/sender.go
Line 319 in 2fa44cb
Combined with #712, this causes any request consistently failing with a retry-able status code to take 90s+ with the default 30s
RetryDuration
on clients (30s for the first request + 60s for the second request). Made only once and without sleeping after, I see the same request take ~3s.The text was updated successfully, but these errors were encountered: