-
Notifications
You must be signed in to change notification settings - Fork 74
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
Instantiate backoff strategy per goroutine #496
Conversation
932d3d1
to
f5d7c57
Compare
/gcbrun |
launcher/container_runner.go
Outdated
MaxInterval = 3600 sec | ||
MaxElapsedTime = 0 (never stops retrying) | ||
WithCappedDuration = 3600 sec | ||
MaxRetries = 8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep the unlimited retry?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my concern is the launcher will hang forever with unlimited retry if refreshToken
keeps returning error. We might want the launcher exit in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvm, this PR will use the original library, so we still keep the unlimited retry.
87ef467
to
2780449
Compare
/gcbrun |
2780449
to
b668068
Compare
b668068
to
342de83
Compare
342de83
to
a3f0425
Compare
/gcbrun |
Instantiate a new backoff object per goroutine since the current retry library is not thread-safe.
This PR also adds those tests related to
RefreshToken
+FetchContainerSignatures
to a test suite with race condition check.