-
Notifications
You must be signed in to change notification settings - Fork 720
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
schedule: fix panic during hot schedule #3483
Conversation
Signed-off-by: Song Gao <disxiaofei@163.com>
b4a9bcb
to
510712c
Compare
Signed-off-by: Song Gao <disxiaofei@163.com>
Codecov Report
@@ Coverage Diff @@
## master #3483 +/- ##
==========================================
+ Coverage 74.57% 74.59% +0.01%
==========================================
Files 244 244
Lines 23981 23982 +1
==========================================
+ Hits 17885 17889 +4
+ Misses 4481 4480 -1
+ Partials 1615 1613 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
@Yisaer: 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. |
This pull request has been accepted and is ready to merge. Commit hash: ccbf4c4
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #3485 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #3486 |
* cherry pick #3483 to release-4.0 Signed-off-by: ti-srebot <ti-srebot@pingcap.com> * fix conflict Signed-off-by: Song Gao <disxiaofei@163.com> Co-authored-by: Song Gao <disxiaofei@163.com> Co-authored-by: Ti Chi Robot <71242396+ti-chi-bot@users.noreply.github.com>
Signed-off-by: Song Gao disxiaofei@163.com
What problem does this PR solve?
hot-region
scheduler may cause PD panic in the following order:storesLoads
before hot region schedulingPutStore
requestraft.cluster
This will cause make
pickDstStores
panic in following code becausestLoadDetail
didn't have the storeID which candidates hold as it was newly put before.What is changed and how it works?
Make the candidates should be searched from
stLoadDetail
during hot region scheduleCheck List
Tests
Release note