You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many requirements for scheduling some jobs periodically in TiDB. For example, TTL needs to schedule a job to delete expired rows every several hours. The implementations look similar in these features, that is: schedule a background "watcher" task in the cluster to check the timer's condition. Once the timer is up to time, then schedule a new job to do something. The "watcher" task will also persist the timer's progress (such as the last job's execution time) to avoid a duplicated job's schedule.
It's better to provide a unified interface to all features with the above requirement.
There are many requirements for scheduling some jobs periodically in TiDB. For example, TTL needs to schedule a job to delete expired rows every several hours. The implementations look similar in these features, that is: schedule a background "watcher" task in the cluster to check the timer's condition. Once the timer is up to time, then schedule a new job to do something. The "watcher" task will also persist the timer's progress (such as the last job's execution time) to avoid a duplicated job's schedule.
It's better to provide a unified interface to all features with the above requirement.
Subtasks
TimerGroupRuntime
to trigger timer events in background #44175TimerStore
#44445Tags
for timer in timer framework #44603mysql.tidb_timers
to manage all timers in tidb #45128README.md
for timer framework #46857The text was updated successfully, but these errors were encountered: