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

GC: delete range could not be executed again if the cleaning rules failed #53369

Open
ystaticy opened this issue May 17, 2024 · 0 comments
Open

Comments

@ystaticy
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Drop table
  2. Wait for the GCWorker leader to run GC logic.
  3. Make delete rules error.
  4. Check rows in mysql.gc_delete_range.
  5. The ranges in mysql.gc_delete_range were deleted, but rules not delete.

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

Records were deleted in mysql.gc_delete_range If cleanup rules encountered an error.

3. What did you see instead (Required)

Do not delete records in mysql.gc_delete_range if the expected rules are not cleaned.

4. What is your TiDB version? (Required)

@ystaticy ystaticy added the type/bug This issue is a bug. label May 17, 2024
@jebter jebter added the sig/transaction SIG:Transaction label May 20, 2024
@ystaticy ystaticy changed the title GC: delete range leaves rules residue GC: delete range could not be executed again if the cleaning rules failed Jun 6, 2024
ti-chi-bot bot pushed a commit that referenced this issue Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants