MGL-66 : Test failure on galera.galera_bf_abort_lock_table #520
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test case changes only. Original test case was expecting certain thd state but as this thd state might be overwritten test was not deterministic. Fixed by using debug sync point in MDL code. When conflicting operation has started to wait conflicting MDL-lock to be released we stop it on sync point and make sure that conflicting LOCK TABLE is not BF aborted because of MDL-conflict.
janlindstrom
force-pushed
the
10.6-MGL-66
branch
from
ff9f4f8 to
cb572a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Test case changes only. Original test case was expecting certain thd state but as this thd state might be overwritten test was not deterministic.
Fixed by using debug sync point in MDL code. When conflicting operation has started to wait conflicting MDL-lock to be released we stop it on sync point and make sure that conflicting LOCK TABLE is not BF aborted because of MDL-conflict.