Fix the problem of configuring multiple gRPC endpoints where the first endpoint times out and cannot switch to the second endpoint #14144
Conversation
This file contains 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
…t endpoint times out and cannot switch to the second endpoint
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 type of PR is this?
What does this PR do? Why is it needed?
In the grpc-go's code, if multiple gRPC endpoints are configured and the first endpoint times out, the subsequent endpoints will also time out, causing the connection to be unable to be re-established. This PR modifies the timeout duration for the subsequent endpoints, so that when the first endpoint times out, the subsequent endpoints can connect normally.
Which issues(s) does this PR fix?
Fixes #14133