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 in refresh algorithm #509

Open
enocom opened this issue Apr 3, 2023 · 0 comments
Open

Use exponential backoff in refresh algorithm #509

enocom opened this issue Apr 3, 2023 · 0 comments
Assignees
@jackwotherspoon
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@enocom
Copy link
Member

enocom commented Apr 3, 2023

Feature Description

On failure, the refresh cycle runs every thirty seconds which can cause cascading failures in high-volume environments when the SQL Admin API quota is breached. This is a request to use exponential backoff with a randomized jitter to prevent thundering herd scenarios.

Sample code

No response

Alternatives Considered

No response

Additional Details

No response
@enocom enocom added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p0 Highest priority. Critical issue. P0 implies highest priority. labels Apr 3, 2023
@enocom enocom removed their assignment Aug 3, 2023
@annafang-google annafang-google self-assigned this Aug 29, 2023
annafang-google added a commit that referenced this issue Aug 29, 2023
@annafang-google
fix: exponential backoff upon refresh failure (#509)
b4519ee
annafang-google added a commit that referenced this issue Aug 29, 2023
@annafang-google
fix: exponential backoff upon refresh failure (#509)
d3d62cb 
Fixed the format
@enocom enocom added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p0 Highest priority. Critical issue. P0 implies highest priority. labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackwotherspoon jackwotherspoon

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@enocom @jackwotherspoon @annafang-google