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

pkg: use minimum interface for schedulers #6553

Merged
merged 3 commits into from
Jun 9, 2023

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Jun 2, 2023

What problem does this PR solve?

Issue Number: Ref #5839.

What is changed and how does it work?

This PR relies on #6551, please review it after #6551 is merged.

It introduces a minimum interface for schedulers. Once all functions within this interface are implemented, we can run the schedulers.

Check List

Tests

  • Unit test

Release note

None.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jun 2, 2023

[REVIEW NOTIFICATION]

This pull request has been approved by:

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

@ti-chi-bot ti-chi-bot bot added the release-note-none Denotes a PR that doesn't merit a release note. label Jun 2, 2023
@ti-chi-bot ti-chi-bot bot requested review from HunDunDM and lhy1024 June 2, 2023 08:57
@rleungx rleungx requested review from JmPotato and nolouch and removed request for lhy1024 and HunDunDM June 2, 2023 09:10
@codecov
Copy link

codecov bot commented Jun 2, 2023

Codecov Report

Patch coverage: 73.68% and project coverage change: +0.03 🎉

Comparison is base (f290e66) 74.66% compared to head (9592b12) 74.69%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6553      +/-   ##
==========================================
+ Coverage   74.66%   74.69%   +0.03%     
==========================================
  Files         417      417              
  Lines       42694    42693       -1     
==========================================
+ Hits        31876    31891      +15     
+ Misses       8007     7995      -12     
+ Partials     2811     2807       -4     
Flag Coverage Δ
unittests 74.69% <73.68%> (+0.03%) ⬆️

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

Impacted Files Coverage Δ
pkg/mock/mockcluster/mockcluster.go 93.83% <ø> (+0.20%) ⬆️
pkg/schedule/checker/merge_checker.go 70.99% <ø> (ø)
pkg/schedule/config/config.go 33.33% <ø> (ø)
pkg/schedule/filter/healthy.go 100.00% <ø> (ø)
pkg/schedule/filter/region_filters.go 86.79% <ø> (ø)
pkg/schedule/operator/create_operator.go 91.77% <ø> (ø)
pkg/schedule/schedulers/balance_region.go 88.02% <ø> (ø)
pkg/schedule/schedulers/balance_witness.go 66.86% <ø> (ø)
pkg/schedule/schedulers/evict_leader.go 81.28% <ø> (-0.99%) ⬇️
pkg/schedule/schedulers/evict_slow_store.go 75.90% <ø> (ø)
... and 20 more

... and 31 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@lhy1024 lhy1024 self-requested a review June 5, 2023 03:43
@ti-chi-bot ti-chi-bot bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 6, 2023
@ti-chi-bot ti-chi-bot bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 6, 2023
@@ -42,17 +42,17 @@ func hasDownPeers(region *core.RegionInfo) bool {
// IsRegionReplicated checks if a region is fully replicated. When placement
// rules is enabled, its peers should fit corresponding rules. When placement
// rules is disabled, it should have enough replicas and no any learner peer.
func IsRegionReplicated(cluster sche.RegionHealthCluster, region *core.RegionInfo) bool {
func IsRegionReplicated(cluster sche.ScheduleCluster, region *core.RegionInfo) bool {
Copy link
Contributor

Choose a reason for hiding this comment

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

sche.ScheduleCluster reads like a stutter

@ti-chi-bot ti-chi-bot bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jun 6, 2023
@ti-chi-bot ti-chi-bot bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jun 8, 2023
@rleungx
Copy link
Member Author

rleungx commented Jun 8, 2023

/merge

1 similar comment
@rleungx
Copy link
Member Author

rleungx commented Jun 9, 2023

/merge

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jun 9, 2023

@rleungx: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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
Contributor

ti-chi-bot bot commented Jun 9, 2023

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

Commit hash: 84beac2

@ti-chi-bot ti-chi-bot bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 9, 2023
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jun 9, 2023

@rleungx: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

Signed-off-by: Ryan Leung <rleungx@gmail.com>
Signed-off-by: Ryan Leung <rleungx@gmail.com>
Signed-off-by: Ryan Leung <rleungx@gmail.com>
@ti-chi-bot ti-chi-bot bot removed the status/can-merge Indicates a PR has been approved by a committer. label Jun 9, 2023
@rleungx
Copy link
Member Author

rleungx commented Jun 9, 2023

/merge

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jun 9, 2023

@rleungx: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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
Contributor

ti-chi-bot bot commented Jun 9, 2023

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

Commit hash: 9592b12

@ti-chi-bot ti-chi-bot bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 9, 2023
@ti-chi-bot ti-chi-bot bot merged commit 181e613 into tikv:master Jun 9, 2023
@rleungx rleungx deleted the split-scheduler branch June 9, 2023 07:32
ti-chi-bot bot added a commit that referenced this pull request Jun 15, 2023
ref #5839, ref #6553

Signed-off-by: Ryan Leung <rleungx@gmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
rleungx added a commit to rleungx/pd that referenced this pull request Dec 1, 2023
ref tikv#5839, ref tikv#6551

Signed-off-by: Ryan Leung <rleungx@gmail.com>
rleungx added a commit to rleungx/pd that referenced this pull request Dec 1, 2023
ref tikv#5839, ref tikv#6553

Signed-off-by: Ryan Leung <rleungx@gmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. 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.

3 participants