scheduler: simplify the limit judgment of hot-region-scheduler

[HunDunDM]

Signed-off-by: HunDunDM hundundm@gmail.com

What problem does this PR solve?

related #3778
changes caused by #3820

What is changed and how it works?

OpLeader and LeaderScheduleLimit are no longer judged in balance-hot-region-scheduler.

Check List

Tests

• Unit test

Code changes

Side effects

Related changes

• Need to cherry-pick to the release branch

Release note

None

[HunDunDM]

/cc @bufferflies

[ti-chi-bot]

@HunDunDM: GitHub didn't allow me to request PR reviews from the following users: bufferflies.

Note that only tikv members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @bufferflies

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 kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #3834 (8d3acfc) into master (4a0970c) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #3834      +/-   ##
==========================================
- Coverage   75.14%   75.09%   -0.06%     
==========================================
  Files         246      246              
  Lines       24740    24723      -17     
==========================================
- Hits        18592    18565      -27     
- Misses       4523     4530       +7     
- Partials     1625     1628       +3     

Flag	Coverage Δ
unittests	75.09% <0.00%> (-0.06%)	⬇️

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

Impacted Files	Coverage Δ
server/schedulers/hot_region.go	84.16% <0.00%> (-0.72%)	⬇️
pkg/tempurl/tempurl.go	45.00% <0.00%> (-25.00%)	⬇️
server/tso/local_allocator.go	80.55% <0.00%> (-9.73%)	⬇️
server/schedulers/shuffle_hot_region.go	54.73% <0.00%> (-9.48%)	⬇️
server/tso/global_allocator.go	70.55% <0.00%> (-5.00%)	⬇️
server/statistics/hot_cache_task.go	79.16% <0.00%> (-4.17%)	⬇️
server/schedulers/random_merge.go	60.00% <0.00%> (-3.34%)	⬇️
client/base_client.go	82.81% <0.00%> (-1.57%)	⬇️
server/member/member.go	68.81% <0.00%> (-1.08%)	⬇️
... and 6 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 4a0970c...8d3acfc. Read the comment docs.

[bufferflies]

lgtm

[nolouch]

lgtm

[nolouch]

cc @lhy1024

[ti-chi-bot]

[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.

[nolouch]

/merge

[ti-chi-bot]

@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]

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

Commit hash: 20690c3

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #3853.

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #3854.

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #3855.