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

Modify placement rule to support witness #5292

Merged
merged 28 commits into from
Oct 20, 2022

Conversation

ethercflow
Copy link
Member

@ethercflow ethercflow commented Jul 10, 2022

Signed-off-by: Wenbo Zhang ethercflow@gmail.com

What problem does this PR solve?

Issue Number: Close #5568

What is changed and how does it work?

Modify placement rule to support witness

Check List

Tests

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

Code changes

  • rule checker

Side effects

  • Increased code complexity

Related changes

Release note

Modify placement rule to support witness

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Jul 10, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • JmPotato
  • rleungx

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 do-not-merge/needs-linked-issue release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jul 10, 2022
server/schedule/checker/rule_checker.go Outdated Show resolved Hide resolved
server/schedule/checker/rule_checker.go Outdated Show resolved Hide resolved
server/core/peer.go Outdated Show resolved Hide resolved
server/schedule/checker/rule_checker_test.go Show resolved Hide resolved
server/schedule/checker/rule_checker.go Outdated Show resolved Hide resolved
server/core/peer.go Show resolved Hide resolved
server/core/peer.go Show resolved Hide resolved
server/schedule/checker/rule_checker.go Outdated Show resolved Hide resolved
@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 27, 2022
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
ref tikv/tikv#12876

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
@rleungx
Copy link
Member

rleungx commented Oct 13, 2022

Will the merge operation be considered in the next PR?

@ethercflow
Copy link
Member Author

Will the merge operation be considered in the next PR?

Yes,I think put it in another PR is better.

go.mod Outdated Show resolved Hide resolved
Copy link
Member

@Connor1996 Connor1996 left a comment

Choose a reason for hiding this comment

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

LGTM overall. Leave for @rleungx to give a approval

ref tikv#5568

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
ref tikv#5568

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 18, 2022
@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 20, 2022
go.mod Outdated Show resolved Hide resolved
ref tikv#5568

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
ref tikv#5568

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
ref tikv#5568

Signed-off-by: Wenbo Zhang <ethercflow@gmail.com>
@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 Oct 20, 2022
@Connor1996
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member

@Connor1996: 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

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

Commit hash: 5148ea8

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Oct 20, 2022
@ti-chi-bot ti-chi-bot merged commit 1a485f7 into tikv:master Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note Denotes a PR that will be considered when it comes time to generate release notes. 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.

Modify placement rule to support witness
5 participants