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: not limit remove peer of the down store (#4097) #4114

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #4097

What problem does this PR solve?

Close #4090.

What is changed and how it works?

This PR adds a flag in the remove peer step to let the store limit not work when the remove store is down.

Check List

Tests

  • Unit test

Release note

None

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Sep 13, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • bufferflies
  • 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 added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved component/schedule Scheduling logic. type/cherry-pick-for-release-5.0 The PR belongs to release-5.0 cherry pick. labels Sep 13, 2021
Copy link
Contributor

@disksing disksing left a comment

Choose a reason for hiding this comment

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

need resolve conflict

close tikv#4090

Signed-off-by: Ryan Leung <rleungx@gmail.com>
Copy link
Contributor

@nolouch nolouch left a comment

Choose a reason for hiding this comment

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

lgtm

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Nov 30, 2021
Copy link
Contributor

@bufferflies bufferflies left a comment

Choose a reason for hiding this comment

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

lgtm

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Nov 30, 2021
@nolouch
Copy link
Contributor

nolouch commented Nov 30, 2021

/merge

@ti-chi-bot
Copy link
Member Author

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

/run-all-tests

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 Author

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

Commit hash: a979ab6

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Nov 30, 2021
@ti-chi-bot
Copy link
Member Author

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.

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.

@rleungx
Copy link
Member

rleungx commented Nov 30, 2021

/run-unit-tests

3 similar comments
@nolouch
Copy link
Contributor

nolouch commented Nov 30, 2021

/run-unit-tests

@nolouch
Copy link
Contributor

nolouch commented Nov 30, 2021

/run-unit-tests

@nolouch
Copy link
Contributor

nolouch commented Nov 30, 2021

/run-unit-tests

@codecov
Copy link

codecov bot commented Nov 30, 2021

Codecov Report

Merging #4114 (508364e) into release-5.0 (a4a4c5a) will decrease coverage by 0.07%.
The diff coverage is 62.96%.

Impacted file tree graph

@@               Coverage Diff               @@
##           release-5.0    #4114      +/-   ##
===============================================
- Coverage        74.87%   74.79%   -0.08%     
===============================================
  Files              245      245              
  Lines            24336    24356      +20     
===============================================
- Hits             18221    18218       -3     
- Misses            4504     4521      +17     
- Partials          1611     1617       +6     
Flag Coverage Δ
unittests 74.79% <62.96%> (-0.08%) ⬇️

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

Impacted Files Coverage Δ
server/schedule/region_scatterer.go 81.61% <0.00%> (-6.87%) ⬇️
server/schedule/checker/replica_strategy.go 88.37% <50.00%> (-4.13%) ⬇️
server/schedulers/shuffle_region.go 75.67% <50.00%> (-1.79%) ⬇️
server/schedule/checker_controller.go 68.29% <100.00%> (+0.79%) ⬆️
server/schedule/operator/builder.go 88.10% <100.00%> (+0.12%) ⬆️
server/schedule/operator/influence.go 85.71% <100.00%> (ø)
server/schedule/operator/step.go 67.65% <100.00%> (+0.21%) ⬆️
server/statistics/store.go 90.67% <100.00%> (ø)
server/schedulers/shuffle_hot_region.go 55.10% <0.00%> (-10.21%) ⬇️
server/member/member.go 63.04% <0.00%> (-6.53%) ⬇️
... and 15 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fcecc89...508364e. Read the comment docs.

@ti-chi-bot ti-chi-bot merged commit 581ee38 into tikv:release-5.0 Nov 30, 2021
@zhouqiang-cl zhouqiang-cl added this to the v5.0.6 milestone Dec 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Cherry pick PR approved by release team. component/schedule Scheduling logic. release-note-none Denotes a PR that doesn't merit a release note. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. triage/accept type/cherry-pick-for-release-5.0 The PR belongs to release-5.0 cherry pick.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants