-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Core: add retry on 503 errors. #5410
Comments
@bmenasha Thanks for the report! @theacodes retrying 503 responses seems reasonable to me. One quick note: the |
A storage copy operation fenced by Retry just failed for me by 503, too. Also, the Please, fix this simple issue, add Ugly hack until the issue is solved: orig_if_transient_error = retry.if_transient_error
retry.if_transient_error = lambda ex: orig_if_transient_error(ex) \
or isinstance(ex, (exceptions.ServiceUnavailable, exceptions.BadGateway))
retry.Retry.__init__ = functools.partialmethod(retry.Retry.__init__, predicate = retry.if_transient_error) |
Also, pin grpcio < 2.0dev. Closes #5410.
@tseaver Thanks for the fix. What about |
The google-api-python-client and gcloud CLI both retry on 503 SERVICE UNAVAILABLE errors yet the current version of google-cloud-python doesn't.
https://github.com/google/google-api-python-client/blob/master/googleapiclient/http.py#L94
We seem to have coded a retry on 500 and 429 , but not 503.
Please consider adding 503 as retryable.
I'm running 2.7.11 but I expect same behavior with 3
The text was updated successfully, but these errors were encountered: