Skip to content
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

Closed
3pointer opened this issue May 27, 2024 · 2 comments · Fixed by #53695
Closed

Log Backup being paused due to a false positive in the automatic lag check. #53561

3pointer opened this issue May 27, 2024 · 2 comments · Fixed by #53695
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. 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
Copy link
Contributor

3pointer commented May 27, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. start a log backup
  2. wait for 48h(the default lag check threshold)
  3. restart tidb advancer(or other scenarios that make advancer owner changed)

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

@3pointer 3pointer added type/bug The issue is confirmed as a bug. component/br This issue is related to BR of TiDB. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. labels May 27, 2024
@ti-chi-bot 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 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
@Leavrth Leavrth added the affects-7.5 This bug affects the 7.5.x(LTS) versions. label Jun 11, 2024
@seiya-annie
Copy link

/found customer

@ti-chi-bot ti-chi-bot bot added the report/customer Customers have encountered this bug. label Jul 5, 2024
@3pointer
Copy link
Contributor Author

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 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. 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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants