Check for fenced old leader in mounted test. - #242
Open
aversecat wants to merge 1 commit into
Open
Conversation
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
October 22, 2025 18:23
08522e5 to
9da6eff
Compare
Collaborator
|
This needs work. |
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
October 23, 2025 19:04
9da6eff to
115ddb4
Compare
Contributor
Author
|
hmmm double free. reworking... |
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
October 31, 2025 16:22
115ddb4 to
a410ae8
Compare
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
2 times, most recently
from
November 20, 2025 18:24
ff0eacb to
5863e67
Compare
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
2 times, most recently
from
December 5, 2025 23:29
e6501c7 to
a87e92c
Compare
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
February 2, 2026 18:21
a87e92c to
2d8f306
Compare
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
March 13, 2026 19:22
2d8f306 to
d84ba60
Compare
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
May 6, 2026 22:23
d84ba60 to
0cbcdab
Compare
The old mounted check only considered begin/end quorum data, and not whether the old leader that is now disconnected was fenced by a new quorum leader. Since this is the guaranteed case if the leader is disconnected forcefully, this check must account for this case, so that quorum slots can be modified if the node is permanently removed or replaced. Signed-off-by: Auke Kok <auke.kok@versity.com>
aversecat
force-pushed
the
auke/utils_check_mounted_quorum_fenced
branch
from
August 13, 2026 18:14
0cbcdab to
33fadd8
Compare
Contributor
Author
|
retest |
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.
The old mounted check only considered begin/end quorum data, and not whether the old leader that is now disconnected was fenced by a new quorum leader.
Since this is the quaranteed case if the leader is disconnected forcefully, this check must account for this case, so that quorum slots can be modified if the node is permanently removed or replaced.
Normally, remounting from the fenced node should clear this. But that may be unwanted, due to e.g. equipment failure, data collection, or otherwise.