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 advancer stop the log backup task when it failed to get global checkpoint ts at the first tick #58031

Closed
Leavrth opened this issue Dec 6, 2024 · 0 comments · Fixed by #58135
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. affects-8.5 This bug affects the 8.5.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

@Leavrth
Copy link
Contributor

Leavrth commented Dec 6, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Another TiDB node becomes new log backup advancer owner.
  2. the --start-ts of the log backup task is recorded as current global checkpoint ts at the first.
  3. the advancer failed to collect the whole region level checkpoint ts, so it can't update the new global checkpoint ts.
  4. it compares the current ts with its recorded global checkpoint ts(--start-ts), and finds that the gap is so large.
  5. Therefore, the advancer stop the log backup task.

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

@Leavrth Leavrth added component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug. labels Dec 6, 2024
@3pointer 3pointer added affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. and removed may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 labels Dec 11, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in e3248e7 Dec 13, 2024
@seiya-annie seiya-annie added the report/customer Customers have encountered this bug. label Dec 18, 2024
@Leavrth Leavrth added affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. labels Dec 23, 2024
@Leavrth Leavrth added the affects-7.5 This bug affects the 7.5.x(LTS) versions. label Dec 23, 2024
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. affects-8.5 This bug affects the 8.5.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.

3 participants