-
Notifications
You must be signed in to change notification settings - Fork 783
client, server: retry follower region misses on leader #11182
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
Open
JmPotato
wants to merge
6
commits into
tikv:master
Choose a base branch
from
JmPotato:fix-query-region-follower-not-found
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7f6899c
client, server: retry follower region misses on leader
JmPotato e84326b
client, server: simplify follower region retry
JmPotato 75c709f
client/router: defer follower misses to next batch
JmPotato 64bc6f7
client/router: allocate retry buffers on demand
JmPotato 196e32b
client/router: isolate leader retry batches
JmPotato 7e05b0a
client/router: refine follower retry coverage
JmPotato File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
id == 0is a definitive empty result, not a follower cache miss. WithWithAllowFollowerHandle, this returnsfound=false, sopartialResponseFinisherretriesGetRegionByID(0)on the leader. If the leader is unavailable, a lookup that should return(nil, nil)instead returns a connection/timeout error. Please finish zero-ID requests directly as nil results and add a follower-path regression test.Uh oh!
There was an error while loading. Please reload this page.
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.
Thanks for pointing this out. I traced the same input through the legacy unary
GetRegionByIDpath and confirmed that it has the same behavior when follower handling is enabled: ifWithAllowFollowerHandleselects a follower,grpcutil.GetRegionByIDreturnsREGION_NOT_FOUNDfor ID 0,ServiceClient.NeedRetrythen retries the request on the leader, and an unavailable leader can therefore surface a connection/timeout error instead of(nil, nil).The compatibility boundary of this PR is to align
QueryRegionwith the existing unary Region-query semantics, rather than change semantics shared by both paths. Special-casing ID 0 only inQueryRegionwould make the two paths diverge. I will keep this PR scoped to parity and handle making zero-ID requests leader-independent for both unary andQueryRegionin a separate follow-up change with coverage for both paths.