You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when repairing down-peer, it will be restricted by store-remove-limit of that store. By default, the upper limit of repairs per hour is 900.
Describe the feature you'd like
Scheduling is not restricted by store-remove-limit of that store when repairing down-peer
* This is an automated cherry-pick of #4097
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
* resolve the conflicts
close#4090
Signed-off-by: Ryan Leung <rleungx@gmail.com>
Co-authored-by: Ryan Leung <rleungx@gmail.com>
rleungx
added a commit
to ti-chi-bot/pd
that referenced
this issue
Nov 30, 2021
* This is an automated cherry-pick of #4097
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
* resolve conflicts
close#4090
Signed-off-by: Ryan Leung <rleungx@gmail.com>
Co-authored-by: Ryan Leung <rleungx@gmail.com>
Feature Request
Describe your feature request related problem
Currently, when repairing down-peer, it will be restricted by store-remove-limit of that store. By default, the upper limit of repairs per hour is 900.
Describe the feature you'd like
Scheduling is not restricted by store-remove-limit of that store when repairing down-peer
Describe alternatives you've considered
Teachability, Documentation, Adoption, Migration Strategy
The text was updated successfully, but these errors were encountered: