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

pd-ctl: add policy selection for split region #1149

Merged
merged 4 commits into from
Jul 18, 2018

Conversation

Connor1996
Copy link
Member

@Connor1996 Connor1996 commented Jul 13, 2018

What have you changed? (required)

Currently TiKV support get approximate middle key from properties, so when split region add a check-policy field to specify to use which way.

What are the type of the changes (required)?

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested (required)?

manual test

Does this PR affect documentation (docs/docs-cn) update? (optional)

pingcap/docs-cn#809

Refer to a related PR or issue link (optional)

pingcap/kvproto#287

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

@disksing
Copy link
Contributor

Do we need to supply to split key to split region too?

@Connor1996
Copy link
Member Author

@disksing No, there is a command for tikv-ctl to split region on specified split key. And this split region command for pd is just half split.

@disksing
Copy link
Contributor

LGTM

@disksing disksing added the DNM label Jul 17, 2018
@disksing
Copy link
Contributor

Please switch to master kvproto before merge.

@Connor1996 Connor1996 removed the DNM label Jul 18, 2018
@Connor1996 Connor1996 merged commit 35de914 into tikv:master Jul 18, 2018
@Connor1996 Connor1996 deleted the add-policy branch July 18, 2018 07:06
nolouch pushed a commit to nolouch/pd that referenced this pull request Aug 15, 2018
* add policy for split region

* update kvproto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants