-
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
store/tikv: not setting special ts when resolving async locks #22723
Conversation
Signed-off-by: Yilin Chen <sticnarf@gmail.com>
Signed-off-by: Yilin Chen <sticnarf@gmail.com>
/run-all-tests |
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
[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 |
|
/run-unit-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 983c39b
|
/merge |
cherry pick to release-5.0 in PR #24397 |
Signed-off-by: Yilin Chen <sticnarf@gmail.com>
What problem does this PR solve?
Issue Number: close #24384
What is changed and how it works?
TiKV always returns the lock information if it is an async-commit lock, so we don't need to set these special ts.
And after setting these timestamps,
check_txn_status
cannot roll back expired locks according tocurrent_ts
, which leads to issue #24384.Related changes
Check List
Tests
Release note