Keep EKV available until fixture shutdown persists dirty state - #32
Merged
Merged
Conversation
This was referenced Sep 9, 2026
jeregrine
force-pushed
the
test/ekv-clean-shutdown
branch
from
September 15, 2026 14:41
ec7ea90 to
45ed2c2
Compare
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
The shared-EKV fixture replaces DurableServer's child spec with a bare map, losing its shutdown budget. The scenario can report success and then tear down its peer/quorum before final persistence, producing forced kills and missing-ETS errors during cleanup.
Fix
Preserve the production child spec and drain both lifecycle managers before stopping durable supervisors, while EKV quorum remains available. Assert normal child termination, supervisor shutdown, the final stopped status, and preservation of dirty state before the peer is removed.
Add a focused single-node fixture-shutdown regression and exercise an unsynced update in the shared-EKV scenario so pre-existing stored state cannot satisfy the final-persistence assertion.