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

rule: prevent misconfiguration of placement rules in some situations (#2481) #2516

Merged
merged 2 commits into from
Jun 5, 2020

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Jun 5, 2020

cherry-pick #2481 to release-4.0


What problem does this PR solve?

Fix #2476

What is changed and how it works?

when update placement rules, return error if after update:

  • there is no rule lest
  • there is gap between rules (region may match no rules)

Check List

Tests

  • Unit test
  • Manual test (add detailed scripts or steps below)

Related changes

  • Need to cherry-pick to the release branch: release-4.0

Release note

  • Prevent misconfiguration of placement rules in some situations

disksing added 2 commits June 5, 2020 17:39
Signed-off-by: disksing <i@disksing.com>
Signed-off-by: disksing <i@disksing.com>
@lhy1024
Copy link
Contributor

lhy1024 commented Jun 5, 2020

/merge

@sre-bot sre-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 5, 2020
@sre-bot
Copy link
Contributor Author

sre-bot commented Jun 5, 2020

Your auto merge job has been accepted, waiting for:

  • 2515

@sre-bot
Copy link
Contributor Author

sre-bot commented Jun 5, 2020

/run-all-tests

@sre-bot sre-bot merged commit e88c246 into tikv:release-4.0 Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/can-merge Indicates a PR has been approved by a committer. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants