-
Notifications
You must be signed in to change notification settings - Fork 773
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
Remove frontend handler retries #3285
Remove frontend handler retries #3285
Conversation
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.
Maybe only land to 1.17 release branch for now? And pick to master after our discussion about the long term solution tomorrow?
We decided not to do this. All commits should go on |
historyClientRetryMaxAttempts = 5 | ||
|
||
matchingClientRetryInitialInterval = 1000 * time.Millisecond | ||
matchingClientRetryMaxAttempts = 2 | ||
matchingClientRetryMaxAttempts = 5 |
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.
Why doing this change?
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.
Because we don't retry on handler level anymore, it makes sense to increase number of attempts from client themselves. 2
is too small for overall retry attempts.
What changed?
Remove frontend handler retries.
Why?
Retries on frontend handler level may lead to unexpected
InvalidArgument
errors. Closes #3282.How did you test it?
Existing tests.
Potential risks
No risks.
Is hotfix candidate?
Yes.