Check cluster isolation through buffered replication and reconnects - #11
Open
jeregrine wants to merge 1 commit into
Open
Check cluster isolation through buffered replication and reconnects#11jeregrine wants to merge 1 commit into
jeregrine wants to merge 1 commit into
Conversation
This was referenced Sep 9, 2026
jeregrine
added this pull request to stack #14
September 9, 2026 20:19
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
1 participant
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.
Problem
A disconnected named cluster can appear correctly empty even if queued replication was incorrectly applied and then purged. Index consistency and final-state checks alone miss the transient lifecycle events, while stale batches and snapshots can also repopulate a cluster after it has been left.
Fix
Add generated scenarios for both registry and PG lanes that prove operations are buffered before disconnect. Require the disconnect path and subsequent batch/snapshot replay to leave the cluster empty without emitting apply-then-purge events.
Vary shard counts, receiver buffers, metadata, and reconnect cycles. Reconnected clusters must accept fresh snapshots, and entries using the same key in the default and another named cluster must survive throughout.
Supporting information
Stacked on #10, following #8. This PR adds only cluster-isolation properties and their snapshot helper, reusing the fixture and history oracle from the preceding PR.
Signals are deliberately delivered to the receiver while owner processes remain alive. This isolates membership gating from network lifecycle behavior; production behavior is unchanged.