Set Backoff.MaxDelay to 10 seconds. #720
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samarabbas
approved these changes
Sep 11, 2020
Contributor
samarabbas
left a comment
samarabbas
left a comment
There was a problem hiding this comment.
This looks ok. But I'm confused as I thought we need MaxBackoff on client-side. This is a server-side change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
gRPC MaxDelay was decreased to 10 seconds from default 120 seconds.
Why?
When failed connection is restored client (another service) needs to know about it faster than 2 minutes.
How did you test it?
Run samples and will test under failures.
Potential risks
No risks.