-
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
Log Backup being paused due to a false positive in the automatic lag check. #53561
Labels
affects-6.5
affects-7.1
affects-7.5
affects-8.1
component/br
This issue is related to BR of TiDB.
report/customer
Customers have encountered this bug.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
3pointer
added
type/bug
The issue is confirmed as a bug.
component/br
This issue is related to BR of TiDB.
affects-6.5
affects-8.1
affects-7.1
labels
May 27, 2024
13 tasks
ti-chi-bot
bot
added
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-7.5
labels
Jun 5, 2024
BornChanger
removed
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-7.5
labels
Jun 5, 2024
This was referenced Jun 11, 2024
/found customer |
this issue was introduced in #50803 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-7.1
affects-7.5
affects-8.1
component/br
This issue is related to BR of TiDB.
report/customer
Customers have encountered this bug.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
a normal log backup status.
3. What did you see instead (Required)
log backup paused by chance.
(The chance is the lastCheckpoint cannot be updated in time before checking. e.g. regions has a hole will make lastCheckpoint skip update this time and wait for next tick. )
4. What is your TiDB version? (Required)
v6.5.9/v7.1.5/v8.1.0/master
The text was updated successfully, but these errors were encountered: