fix: mongodb leader fallback and single-member reconfig#17
Merged
Conversation
1b0526f to
e773f9f
Compare
zijiren233
approved these changes
Apr 8, 2026
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
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.
Summary
Fix MongoDB scale-in failures (cluster has no leader) in KB 0.9.x by adding leader fallback, single-member reconfig, and join-member de-dup logic in lorry.
What changed
Why
In KB 0.9.x the MongoDB HA loop is disabled, so leader leases are not renewed. Scale-in operations that depend on a leader fail and can leave the cluster stuck in Updating. Single-member replicasets can also
remain SECONDARY without a forced reconfig.
Scope
Validation