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

TTL table may not have change to schedule when the whole TTL schedule is heavy #57137

Closed
lcwangchao opened this issue Nov 5, 2024 · 0 comments · Fixed by #57067
Closed

TTL table may not have change to schedule when the whole TTL schedule is heavy #57137

lcwangchao opened this issue Nov 5, 2024 · 0 comments · Fixed by #57067
Labels
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/major type/bug The issue is confirmed as a bug.

Comments

@lcwangchao
Copy link
Collaborator

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. create 1000+ TTL tables and each table's ttl_job_schedule_interval is set to 1m
  2. wait about 30 minutes
  3. check whether any TTL table's schedule is delayed for a long time by
select now(),watermark, TIMESTAMPDIFF(minute, watermark, now()) from mysql.tidb_timers where TIMESTAMPDIFF(minute, watermark, now()) > 20 limit 1;

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

No rows found

3. What did you see instead (Required)

TiDB [email protected]:(none)> select now(),watermark, TIMESTAMPDIFF(minute, watermark, now()) from mysql.tidb_timers where TIMESTAMPDIFF(minute, watermark, now()) > 20 limit 1;
+---------------------+---------------------+-----------------------------------------+
| now()               | watermark           | TIMESTAMPDIFF(minute, watermark, now()) |
+---------------------+---------------------+-----------------------------------------+
| 2024-11-05 09:56:12 | 2024-11-05 09:33:41 | 22                                      |
+---------------------+---------------------+-----------------------------------------+

You can see, some table's schedule is delayed by about 20+ minutes...

4. What is your TiDB version? (Required)

@lcwangchao lcwangchao added type/bug The issue is confirmed as a bug. severity/major labels Nov 5, 2024
@lcwangchao lcwangchao added 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. 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 Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant