Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use exponential backoff on test/sample admin requests to harden against RESOURCE_EXHAUSTED test failures #483

Open
larkee opened this issue Aug 11, 2021 · 0 comments
Open

Use exponential backoff on test/sample admin requests to harden against RESOURCE_EXHAUSTED test failures #483

larkee opened this issue Aug 11, 2021 · 0 comments
Labels
api: spanner Issues related to the googleapis/python-spanner API. samples Issues that are directly related to samples. type: process A process-related concern. May include testing, release, or the like.

Comments

@larkee
Copy link
Contributor

larkee commented Aug 11, 2021

Currently, when multiple PRs run the samples + system tests at similar times, the PRs will have RESOURCE_EXHAUSTED failures due to exceeding the admin request per minute quota.

As per googleapis/nodejs-spanner#958, the recommendation is to:

implement exponential back-off with extended total timeout and number of re-tries for admin operations
@product-auto-label product-auto-label bot added api: spanner Issues related to the googleapis/python-spanner API. samples Issues that are directly related to samples. labels Aug 11, 2021
@larkee larkee added the type: process A process-related concern. May include testing, release, or the like. label Aug 12, 2021
@hadim hadim mentioned this issue Aug 22, 2021
Closed
@larkee larkee removed their assignment Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api: spanner Issues related to the googleapis/python-spanner API. samples Issues that are directly related to samples. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@larkee