scheduler: fix policy with write-leader in hot scheduler

[HunDunDM]

Signed-off-by: HunDunDM [email protected]

What problem does this PR solve?

Issue Number: Ref #4949

What is changed and how does it work?

The write leader dimension only compares the first dimension when it is good, and should only compare the first dimension when filtering.

Check List

Tests

Release note

None

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

[codecov]

Codecov Report

Base: 75.58% // Head: 75.59% // Increases project coverage by +0.01% 🎉

Coverage data is based on head (c053d5b) compared to base (1218b4d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5526      +/-   ##
==========================================
+ Coverage   75.58%   75.59%   +0.01%     
==========================================
  Files         323      323              
  Lines       31992    32000       +8     
==========================================
+ Hits        24181    24191      +10     
- Misses       5721     5722       +1     
+ Partials     2090     2087       -3     

Flag	Coverage Δ
unittests	75.59% <100.00%> (+0.01%)	⬆️

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

Impacted Files	Coverage Δ
server/schedulers/hot_region.go	85.73% <100.00%> (-0.11%)	⬇️
pkg/dashboard/keyvisual/input/core.go	0.00% <0.00%> (-33.34%)	⬇️
...erver/config/service_middleware_persist_options.go	91.66% <0.00%> (-8.34%)	⬇️
server/election/leadership.go	75.25% <0.00%> (-3.10%)	⬇️
tools/pd-ctl/pdctl/command/operator.go	66.66% <0.00%> (-1.15%)	⬇️
server/region_syncer/server.go	81.86% <0.00%> (-1.10%)	⬇️
server/statistics/hot_peer_cache.go	96.09% <0.00%> (-0.79%)	⬇️
server/config/persist_options.go	92.73% <0.00%> (-0.67%)	⬇️
server/handler.go	52.70% <0.00%> (-0.39%)	⬇️
server/server.go	75.56% <0.00%> (-0.26%)	⬇️
... and 21 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

[nolouch]

lgtm

[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: c053d5b