enhance: retry grpc errors with custom retry policy - #195
Closed
ShuranZhang wants to merge 1 commit into
Closed
Conversation
ShuranZhang
force-pushed
the
unavailable-err
branch
from
August 14, 2025 18:07
5776be9 to
d1fe641
Compare
ShuranZhang
force-pushed
the
unavailable-err
branch
from
August 14, 2025 22:35
d1fe641 to
a26593e
Compare
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
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.
Also modify custom retry policy to retry on same node for unavailable errors, since Spanner is interpreted as a single node Cassandra server.