-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Circuit breaker log backup task when checkpoint ts does not advance for a long time #50803
Comments
/assign @RidRisR |
@BornChanger: GitHub didn't allow me to assign the following users: RidRisR. Note that only pingcap members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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 kubernetes/test-infra repository. |
/assign @RidRisR |
@BornChanger: GitHub didn't allow me to assign the following users: RidRisR. Note that only pingcap members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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 kubernetes/test-infra repository. |
/assign @RidRisR |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
log backup stop advance by whatever reason. (usually it caused by a bug like tikv/tikv#16056). eventually we need a protection mechanism.
2. What did you expect to see? (Required)
log backup won't block GC for a long time.
3. What did you see instead (Required)
log backup block GC for a month.
4. What is your TiDB version? (Required)
below 6.5.6
The text was updated successfully, but these errors were encountered: