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

scheduler: allow empty region to be scheduled and use a sperate tolerance config in scatter range scheduler (#4106) #4118

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #4106

What problem does this PR solve?

  1. we expect the tolerance ratio in range cluster should be 2, but it doesn't take effect.

    c.SetTolerantSizeRatio(2)

    tolerantSizeRatio := cluster.GetOpts().GetTolerantSizeRatio()

  2. we expect it can schedule empty region, but it can not and test can not detect

    EmptyRegionApproximateSize = 1

    // empty case
    regions[49].EndKey = []byte("")
    for _, meta := range regions {
    leader := rand.Intn(4) % 3
    regionInfo := core.NewRegionInfo(
    meta,
    meta.Peers[leader],
    core.SetApproximateKeys(96),
    core.SetApproximateSize(96),

What is changed and how it works?

allow empty region to be scheduled and use a sperate tolerance config in scatter range scheduler

Check List

Tests

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

Add scatter range scheduler

Before this pr
image
After this pr
image

Related changes

  • Need to cherry-pick to the release branch

Release note

allow empty region to be scheduled and use a sperate tolerance config in scatter range scheduler

…ance config in scatter range scheduler

Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
Signed-off-by: lhy1024 <admin@liudos.us>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Sep 13, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • disksing
  • 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.

@codecov
Copy link

codecov bot commented Sep 13, 2021

Codecov Report

Merging #4118 (bcce372) into release-5.2 (24d1383) will increase coverage by 0.07%.
The diff coverage is 100.00%.

Impacted file tree graph

@@               Coverage Diff               @@
##           release-5.2    #4118      +/-   ##
===============================================
+ Coverage        74.65%   74.72%   +0.07%     
===============================================
  Files              249      249              
  Lines            25539    25550      +11     
===============================================
+ Hits             19065    19092      +27     
+ Misses            4788     4772      -16     
  Partials          1686     1686              
Flag Coverage Δ
unittests 74.72% <100.00%> (+0.07%) ⬆️

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

Impacted Files Coverage Δ
server/schedulers/balance_region.go 88.69% <100.00%> (+0.62%) ⬆️
server/schedulers/utils.go 94.46% <100.00%> (+0.08%) ⬆️
server/schedulers/shuffle_hot_region.go 55.55% <0.00%> (-10.11%) ⬇️
server/tso/local_allocator.go 71.62% <0.00%> (-6.76%) ⬇️
pkg/etcdutil/etcdutil.go 84.70% <0.00%> (-3.53%) ⬇️
pkg/dashboard/adapter/manager.go 79.78% <0.00%> (-3.20%) ⬇️
server/schedule/operator/step.go 67.44% <0.00%> (-1.67%) ⬇️
client/base_client.go 82.81% <0.00%> (-1.57%) ⬇️
server/tso/tso.go 60.22% <0.00%> (-1.11%) ⬇️
server/schedule/operator_controller.go 84.75% <0.00%> (-0.80%) ⬇️
... and 10 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 24d1383...bcce372. Read the comment docs.

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 14, 2021
@zhouqiang-cl zhouqiang-cl added the cherry-pick-approved Cherry pick PR approved by release team. label Oct 12, 2021
@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 13, 2021
@nolouch
Copy link
Contributor

nolouch commented Oct 13, 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: e592319

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Oct 13, 2021
@ti-chi-bot ti-chi-bot merged commit 6f3ff3f into tikv:release-5.2 Oct 13, 2021
@zhouqiang-cl zhouqiang-cl added this to the v5.2.2 milestone Oct 20, 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/scheduler Scheduler logic. 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. type/cherry-pick-for-release-5.2 The PR belongs to release-5.2 cherry pick.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants