[close #736] Select reachable store (#737)#742
Merged
zhangyangyu merged 3 commits intotikv:release-3.3from Apr 27, 2023
Merged
Conversation
close tikv#736 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> Signed-off-by: shiyuhang <1136742008@qq.com>
Signed-off-by: shiyuhang <1136742008@qq.com>
shiyuhang0
force-pushed
the
cherry-pick-737-to-release-3.3
branch
from
afc190b to
b82155a
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-3.3 #742 +/- ##
==============================================
Coverage ? 37.90%
Complexity ? 1608
==============================================
Files ? 278
Lines ? 17493
Branches ? 1989
==============================================
Hits ? 6630
Misses ? 10198
Partials ? 665 ☔ View full report in Codecov by Sentry. |
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
3 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.
This is an automated cherry-pick of #737
What problem does this PR solve?
Issue Number: close #736
What is changed and how does it work?
Judge store status before use. Use the next replica when the current replica is unreachable.
Test
I have tested in TiSpark follower read with the first store killed, its success to request the next store.