checker: avoid unnecessary remove disconnected peer with multi orphan peers#7315
checker: avoid unnecessary remove disconnected peer with multi orphan peers#7315ti-chi-bot[bot] merged 9 commits intotikv:masterfrom
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Signed-off-by: lhy1024 <admin@liudos.us>
Codecov Report
@@ Coverage Diff @@
## master #7315 +/- ##
==========================================
- Coverage 74.49% 74.46% -0.03%
==========================================
Files 446 446
Lines 48346 48352 +6
==========================================
- Hits 36016 36007 -9
- Misses 9160 9165 +5
- Partials 3170 3180 +10
Flags with carried forward coverage won't be shown. Click here to find out more. |
| return operator.CreateDemoteLearnerOperatorAndRemovePeer("replace-down-peer-with-orphan-peer", c.cluster, region, orphanPeer, pinDownPeer) | ||
| case orphanPeerRole == metapb.PeerRole_Voter && destRole == metapb.PeerRole_Voter && | ||
| isDisconnectedPeer(pinDownPeer) && !dstStore.IsDisconnected(): | ||
| case orphanPeerRole == destRole && isDisconnectedPeer(pinDownPeer) && !dstStore.IsDisconnected(): |
There was a problem hiding this comment.
allow replace learner
| if hasHealthPeer { | ||
| // there already exists a healthy orphan peer, so we can remove other orphan Peers. | ||
| ruleCheckerRemoveOrphanPeerCounter.Inc() | ||
| // if there exists a disconnected orphan peer, we will pick it to remove firstly. |
There was a problem hiding this comment.
avoid to remove normal peer
There was a problem hiding this comment.
Consider that we have 3 orphan peer, two healthy and one disconnected. Is it possiable that we remove a healthy peer first?
There was a problem hiding this comment.
Should we always remove disconnected peer first?
There was a problem hiding this comment.
Should we always remove disconnected peer first?
I think so.
|
@rleungx PTAL |
Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
|
/merge |
|
@lhy1024: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: f12d0b4 |



What problem does this PR solve?
Issue Number: Close #7249
When there are many orphan peers, we don't think disconnected peer are healthy
And when we decide to remove peer, we will pick disconnected peer firstly.
What is changed and how does it work?
Check List
Tests
Release note