tikv: eliminate unnecessary pessimistic rollback (#12561) #12707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #12561 to release-3.0
Signed-off-by: youjiali1995 zlwgx1023@gmail.com
What problem does this PR solve?
When acquiring pessimistic locks fails, we do async pessimistic rollback to clean up all locks even some of them are not locked. These rollback operations will conflict with the following lock operations which may reduce performance.
What is changed and how it works?
If there is only 1 key and lock failed, no need to do pessimistic rollback.
sysbench oltp_write_only, tables: 32*100, threads: 128
Before
This PR
Check List
Tests
Code changes
Side effects
Related changes
Release note