-
Notifications
You must be signed in to change notification settings - Fork 724
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
checker: fix unhealth region skip the rule check #6427
Conversation
Signed-off-by: nolouch <[email protected]>
[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. Reviewer can indicate their review by submitting an approval review. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #6427 +/- ##
=======================================
Coverage 75.11% 75.11%
=======================================
Files 409 409
Lines 41484 41488 +4
=======================================
+ Hits 31160 31165 +5
- Misses 7630 7634 +4
+ Partials 2694 2689 -5
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
@@ -424,14 +423,6 @@ func (oc *OperatorController) checkAddOperator(isPromoting bool, ops ...*operato | |||
if op.SchedulerKind() == operator.OpAdmin || op.IsLeaveJointStateOperator() { | |||
continue | |||
} | |||
if cl, ok := oc.cluster.(interface{ GetRegionLabeler() *labeler.RegionLabeler }); ok { |
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.
It seems we need to use the way of pausing schedulers to prevent the range from being scheduled.
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.
I add the tests, prevent it in coordinator
.
Signed-off-by: nolouch <[email protected]>
Signed-off-by: nolouch <[email protected]>
Signed-off-by: nolouch <[email protected]>
Signed-off-by: nolouch <[email protected]>
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.
rest LGTM
Signed-off-by: nolouch <[email protected]>
/merge |
@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. |
This pull request has been accepted and is ready to merge. Commit hash: 1abc0e5
|
In response to a cherrypick label: new pull request created to branch |
close tikv#6426 Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
close #6426, ref #6427 allow the `schedule=deny` label can do rule constraints check Signed-off-by: nolouch <[email protected]> Co-authored-by: nolouch <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
close tikv#6426 allow the `schedule=deny` label can do rule constraints check Signed-off-by: nolouch <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
close #6426, ref #6427 allow the `schedule=deny` label can do rule constraints check Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: nolouch <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: ShuNing <[email protected]> Co-authored-by: nolouch <[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>
In response to a cherrypick label: new pull request created to branch |
close tikv#6426 Signed-off-by: ti-chi-bot <[email protected]>
close #6426 allow the `schedule=deny` label can do rule constraints check Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: nolouch <[email protected]> Co-authored-by: ShuNing <[email protected]> Co-authored-by: nolouch <[email protected]>
…kv#6427 Signed-off-by: Shirly <[email protected]>
What problem does this PR solve?
Issue Number: Close #6426
What is changed and how does it work?
Check List
Tests
Release note