-
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
Datastore: 'ServiceUnavailable: 503 Connect Failed' raised during commit #6121
Comments
I have the same issue with google vision api. |
@maxbellec The traceback shows that the @DowneyTung |
@tseaver cool..thanks.. :) |
@tseaver thank you for looking into my issue. I'm still unsure about why that errors happens quite often in the first place. I'm especially surprised that it happens only in the CI tests, do you have any guess on what I could try? |
@pcostell Can you suggest why the 503 is being raised from the Datastore API here? Should we be retrying the |
Needs help from @pcostell or another resource from the back-end Datastore team. |
@maxbellec I think you can close this issue. |
@corradio Thanks very much for the follow up. |
During our CI (run by Strider CD in a container), we put some entities on the Datastore. For reasons I don't understand, it often fails (~30% of the time) with a 503 error. Re-testing (relaunching a new container and running the tests) fixes it.
I'm not sure #5410 would fix this issue, since retrying with
try/except
in the code doesn't solve this.versions
stacktrace
The text was updated successfully, but these errors were encountered: