Fix deadlock happen in mvcc.#3911
Fix deadlock happen in mvcc.#3911ti-chi-bot merged 5 commits intopingcap:masterfrom jiaqizho:fix-deadlock-in-apply
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. DetailsReviewer can indicate their review by submitting an approval review. |
JaySon-Huang
left a comment
There was a problem hiding this comment.
LGTM with small comments
Co-authored-by: JaySon <jayson.hjs@gmail.com>
Co-authored-by: JaySon <jayson.hjs@gmail.com>
|
/merge |
|
@jiaqizho: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. DetailsInstructions 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 pull request has been accepted and is ready to merge. DetailsCommit hash: f52c9a6 |
|
/run-unit-test |
|
Coverage detail: https://ci-internal.pingcap.net/job/tics_ghpr_unit_test/1089/cobertura/ lines: 44.7% (51528 out of 115216) |
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
mvccapply awritebatchwithin arefanddelrefsame asdel(or put)applymethod will get the lock first. and inrefop, will get a lock again.What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note