-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
ddl: stop DDL retry when partition ID is not found in truncate partition
(#26232)
#26238
ddl: stop DDL retry when partition ID is not found in truncate partition
(#26232)
#26238
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
[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-all-tests |
@tangenta you're already a collaborator in bot's repo. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5023da1
|
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests 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. |
cherry-pick #26232 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/26238
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #26229
Problem Summary:
Before this PR,
TRUNCATE PARTITION
DDL job use partition ID as the job argument.Since the truncating implementation is to drop old partition and then add a new partition, the partition ID is changed between two
job. However, it is possible that there are 2 same "truncate" job occurs in the DDL job queue, because they are enqueued by different TiDB server.
In this case, the argument(partition ID) of the second job becomes invalid. Finally the error 'partition not found' is reported.
What is changed and how it works?
What's Changed: Use partition name instead of ID as the job argument.
Check List
Tests
Side effects
Documentation
NA
Release note