Skip to content
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

schedule: fix the down peer cannot be repaired #7996

Merged
merged 2 commits into from
Apr 10, 2024

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Mar 28, 2024

What problem does this PR solve?

Issue Number: Close #7808.

What is changed and how does it work?

Check List

Tests

  • Unit test

Release note

None.

Copy link
Contributor

ti-chi-bot bot commented Mar 28, 2024

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • CabinfeverB
  • nolouch

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-triage-completed release-note-none Denotes a PR that doesn't merit a release note. labels Mar 28, 2024
@ti-chi-bot ti-chi-bot bot requested review from JmPotato and lhy1024 March 28, 2024 09:19
@ti-chi-bot ti-chi-bot bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 28, 2024
@rleungx rleungx requested review from nolouch and CabinfeverB and removed request for lhy1024 March 28, 2024 09:20
Copy link

codecov bot commented Mar 28, 2024

Codecov Report

Merging #7996 (f186939) into master (2b8116e) will decrease coverage by 3.89%.
The diff coverage is 100.00%.

❗ Current head f186939 differs from pull request most recent head 6f425bc. Consider uploading reports for the commit 6f425bc to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7996      +/-   ##
==========================================
- Coverage   77.31%   73.42%   -3.89%     
==========================================
  Files         468      436      -32     
  Lines       60867    48478   -12389     
==========================================
- Hits        47058    35594   -11464     
+ Misses      10273     9823     -450     
+ Partials     3536     3061     -475     
Flag Coverage Δ
unittests 73.42% <100.00%> (-3.89%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@@ -98,7 +98,12 @@ func (s *ReplicaStrategy) SelectStoreToFix(coLocationStores []*core.StoreInfo, o
}
// trick to avoid creating a slice with `old` removed.
s.swapStoreToFirst(coLocationStores, old)
return s.SelectStoreToAdd(coLocationStores[1:])
// If the coLocationStores only has one store, no need to remove.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In issue desc, there are 3 nodes labeled disk_type=mix. Does it affect 3 nodes case?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean 3 nodes case?

@ti-chi-bot ti-chi-bot bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 9, 2024
@ti-chi-bot ti-chi-bot bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Apr 10, 2024
@nolouch
Copy link
Contributor

nolouch commented Apr 10, 2024

/merge

Copy link
Contributor

ti-chi-bot bot commented Apr 10, 2024

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions 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.

Copy link
Contributor

ti-chi-bot bot commented Apr 10, 2024

This pull request has been accepted and is ready to merge.

Commit hash: f186939

@ti-chi-bot ti-chi-bot bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 10, 2024
@CabinfeverB
Copy link
Member

/check-issue-triage-complete

@CabinfeverB
Copy link
Member

/merge

Copy link
Contributor

ti-chi-bot bot commented Apr 10, 2024

@CabinfeverB: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions 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.

@ti-chi-bot ti-chi-bot bot merged commit fecffc3 into tikv:master Apr 10, 2024
22 checks passed
@rleungx rleungx deleted the fix-replace branch April 10, 2024 08:10
@Smityz
Copy link
Contributor

Smityz commented Apr 10, 2024

Thank you! @rleungx

@rleungx
Copy link
Member Author

rleungx commented Apr 10, 2024

Thank you! @rleungx

Can you try it again?

@Smityz
Copy link
Contributor

Smityz commented Apr 10, 2024

Thank you! @rleungx

Can you try it again?

I will try later

@lhy1024
Copy link
Contributor

lhy1024 commented May 20, 2024

/cherry-pick release-6.5

@lhy1024
Copy link
Contributor

lhy1024 commented May 20, 2024

/cherry-pick release-7.1

@lhy1024
Copy link
Contributor

lhy1024 commented May 20, 2024

/cherry-pick release-7.5

@lhy1024
Copy link
Contributor

lhy1024 commented May 20, 2024

/cherry-pick release-8.1

@ti-chi-bot
Copy link
Member

@lhy1024: new pull request created to branch release-6.5: #8195.

In response to this:

/cherry-pick release-6.5

Instructions 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.

@ti-chi-bot
Copy link
Member

@lhy1024: new pull request created to branch release-7.1: #8196.

In response to this:

/cherry-pick release-7.1

Instructions 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.

@ti-chi-bot
Copy link
Member

@lhy1024: new pull request created to branch release-7.5: #8197.

In response to this:

/cherry-pick release-7.5

Instructions 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.

@ti-chi-bot
Copy link
Member

@lhy1024: new pull request created to branch release-8.1: #8198.

In response to this:

/cherry-pick release-8.1

Instructions 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.

ti-chi-bot bot pushed a commit that referenced this pull request May 28, 2024
close #7808

Signed-off-by: Ryan Leung <[email protected]>

Co-authored-by: Ryan Leung <[email protected]>
Co-authored-by: lhy1024 <[email protected]>
ti-chi-bot bot added a commit that referenced this pull request May 28, 2024
close #7808

Signed-off-by: Ryan Leung <[email protected]>

Co-authored-by: Ryan Leung <[email protected]>
Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ti-chi-bot bot pushed a commit that referenced this pull request Jun 4, 2024
ti-chi-bot bot added a commit that referenced this pull request Sep 10, 2024
close #7808

Signed-off-by: Ryan Leung <[email protected]>

Co-authored-by: Ryan Leung <[email protected]>
Co-authored-by: ShuNing <[email protected]>
Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Down-peer-region can't recover when enable placement-rule policy
6 participants