Properly update node allocator state on release #12435
Merged
losipiuk merged 3 commits intotrinodb:masterfrom May 18, 2022
Merged
Properly update node allocator state on release #12435losipiuk merged 3 commits intotrinodb:masterfrom
losipiuk merged 3 commits intotrinodb:masterfrom
Conversation
Statement ordering was incorrect previously and routine to process pending acquires was woken up before whole state related to released node was updated. It could still be observed by routine that released node is occupied and pending acquire was not fulfilled.
losipiuk
force-pushed
the
lo/bin-packing-test-fixes
branch
from
c5acc8f to
746b65e
Compare
arhimondr
approved these changes
May 17, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
fix
core query engine
Related issues, pull requests, and links
Fixes: #12415
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:
(negligible chance that impact of this issue was visible to any user)