domain: add resolve lock logic for mvcc get key loading schema diff (#48330) #48415
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.
This is an automated cherry-pick of #48330
What problem does this PR solve?
Issue Number: close #48281 ref #47807
Problem Summary:
Handle lock error getting schema diff key using mvcc interfaces to avoid unexpected schema cache invalidation.
What is changed and how it works?
Check List
Tests
Running concurrent DDL with stale read requests with injected slow internal transaction commit, there's no
mvcc get
errors reported, the test result is in the description of this PRSide effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.