timer
will keep waiting for job if it exists in history but not exists in status and the owner stopped.
#58510
Labels
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.
severity/moderate
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)
tidb_ttl_table_status
andtidb_ttl_job_history
are created, drop the table.After a while, the owner will remove the job (as the logic in
(*JobManager).checkNotOwnJob()
), and nobody will update the history anymore.Then the timer will always find the job because the entry in
tidb_ttl_job_history
still exists, and wait for it to finish.2. What did you expect to see? (Required)
Don't spawn new goroutine to wait for these not exist tables.
3. What did you see instead (Required)
Keeps waiting for the TTL job for non-exist table to finish.
The text was updated successfully, but these errors were encountered: