-
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 database slow and lots of "scatter region failed, retring" in log when stores less then replica #27425
Comments
Because of pingcap/br#1402, when a region hasn't been full replicated, BR would retry scatter until it was fully replicated. However, unfortunately, when there aren't enough stores, this would always fail, and backoff time would become unreasonable. We can skip scatter in this condition to solve this. |
BTW, you can set pd-ctl config set max-replicas 1 |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
1 tidb, 1 pd, 1 tikv
2. What did you expect to see? (Required)
restore success
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: