-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
br restore hang #27534
Comments
The root cause is the same as #27425. |
The issue is still not fixed with the latest PR.
|
This is caused by the placement rules. #27483 has fixed the problem by comparing The simplest way to fix it is the "Plan B" of fixing #27425: the root reason of being stuck is we scatter region sequentially: Lines 284 to 297 in e52dbd6
If we call the scatter requests parallel or just move the scatter call outside the for loop and just call the batch version of scatter: 'ScatterRegions'. BR won't be stuck more than one full retry. BTW, BR only get stuck at a unhealthy cluster (with many regions lose peer). IMO, maybe this bug shouldn't be so critical... |
Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
tiup br:nightly restore db --db=test --pd xxxx:2679 --storage s3://benchmark/sysbench-32-10000000 --s3.endpoint http://xxx:9000 --send-credentials-to-tikv=true
2. What did you expect to see? (Required)
br successfully
3. What did you see instead (Required)
br does not exit with log
4. What is your TiDB version? (Required)
nightly
Release Version: v5.1.1
Edition: Community
Git Commit Hash: 797bddd
Git Branch: heads/refs/tags/v5.1.1
UTC Build Time: 2021-07-28 11:00:26
GoVersion: go1.16.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
The text was updated successfully, but these errors were encountered: