-
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
txn: avoid the gc resolving pessimistic locks of ongoing transactions (#24601) #24652
txn: avoid the gc resolving pessimistic locks of ongoing transactions (#24601) #24652
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@cfzjywxk please accept the invitation then you can push to the cherry-pick pull requests. |
[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 writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5465c62
|
@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 #24601 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/24652
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #24591
Problem Summary:
The pessimistic locks of ongoing transaction may be resolved by the gc worker and the user will not be aware of this during execution.
What is changed and how it works?
What's Changed:
Decrement the minStartTS by one setting the safepoint so that the locks of ongoing transaction would not be collected by this gc round.
How it Works:
Related changes
Check List
Tests
Side effects
Release note