*: fix scheduling can not immediately start after transfer leader (#4875)

[ti-chi-bot]

This is an automated cherry-pick of #4875

Signed-off-by: Ryan Leung [email protected]

What problem does this PR solve?

Issue Number: Close #4769.

What is changed and how does it work?

This PR uses the flag to distinguish if the region's heartbeat is new when transferring the PD leader.

Check List

Tests

• Unit test

Release note

Fix the issue that scheduling cannot immediately start after PD leader transfers

[ti-chi-bot]

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

Codecov Report

Merging #4973 (7c78c7e) into release-5.0 (498d5db) will increase coverage by 0.09%.
The diff coverage is 89.28%.

@@               Coverage Diff               @@
##           release-5.0    #4973      +/-   ##
===============================================
+ Coverage        74.82%   74.92%   +0.09%     
===============================================
  Files              245      245              
  Lines            24456    24473      +17     
===============================================
+ Hits             18300    18336      +36     
+ Misses            4528     4515      -13     
+ Partials          1628     1622       -6     

Flag	Coverage Δ
unittests	74.92% <89.28%> (+0.09%)	⬆️

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

Impacted Files	Coverage Δ
server/region_syncer/client.go	79.84% <50.00%> (+0.15%)	⬆️
server/cluster/cluster.go	81.81% <87.50%> (-0.20%)	⬇️
server/cluster/coordinator.go	75.52% <100.00%> (+0.11%)	⬆️
server/core/region.go	90.68% <100.00%> (+0.07%)	⬆️
server/core/region_option.go	81.81% <100.00%> (+0.42%)	⬆️
server/grpc_service.go	47.39% <100.00%> (+0.79%)	⬆️
pkg/dashboard/adapter/manager.go	78.72% <0.00%> (-4.26%)	⬇️
server/member/member.go	65.21% <0.00%> (-3.27%)	⬇️
server/election/leadership.go	83.52% <0.00%> (-2.36%)	⬇️
server/tso/allocator_manager.go	74.25% <0.00%> (-1.17%)	⬇️
... and 13 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 498d5db...7c78c7e. Read the comment docs.

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

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.