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

Make request exponential backoff more predictable #359

Closed
hausdorff opened this issue Jan 19, 2019 · 0 comments
Closed

Make request exponential backoff more predictable #359

hausdorff opened this issue Jan 19, 2019 · 0 comments
Assignees
@lblackstone
Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally kind/bug Some behavior is incorrect or out of spec p1 A bug severe enough to be the next item assigned to an engineer
Milestone
0.21

Comments

@hausdorff
Copy link
Contributor

Since #348 request retry logic is specified in multiple places. This can make retry logic much less predictable -- it is vastly easier to predict behavior when retry logic is specified in one place.

Before the next release, we should try to consolidate this into one place. Context: #348 (comment)
@hausdorff hausdorff added kind/bug Some behavior is incorrect or out of spec priority/P1 area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally labels Jan 19, 2019
@hausdorff hausdorff added this to the 0.21 milestone Jan 19, 2019
@lblackstone lblackstone mentioned this issue Jan 23, 2019
Merged
@infin8x infin8x added the p1 A bug severe enough to be the next item assigned to an engineer label Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lblackstone lblackstone

Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally kind/bug Some behavior is incorrect or out of spec p1 A bug severe enough to be the next item assigned to an engineer
Projects
None yet
Milestone
0.21
Development

No branches or pull requests
3 participants
@infin8x @hausdorff @lblackstone