-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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: implement ttl job schedule framework (#39472) #39830
ttl: implement ttl job schedule framework (#39472) #39830
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-build |
1 similar comment
/run-build |
/run-all-tests |
1 similar comment
/run-all-tests |
97f8307
to
8892bc3
Compare
This PR depends on #39775 |
8892bc3
to
ee09fed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-unit-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: ee09fed
|
@ti-chi-bot: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This is an automated cherry-pick of #39472
What problem does this PR solve?
Issue Number: close #39471
Problem Summary:
Implement a ttl job schedule framework. It reads information from the info schema and the
mysql.tidb_ttl_table_status
, gets the job to run and schedule them to a scan worker.The implementation of variable settings,
scanWorker
anddelWorker
are left for future development.What is changed and how it works?
For most parts, the job manager is split from the original demo: https://github.com/pingcap/tidb/pull/39320/files. It implements the following feature:
This pr left a lot of TODO for system variables. They are left in #39727.
Check List
Tests