fix(common): gracefully drain leader pushes on shutdown - #1440
Draft
schickling wants to merge 3 commits into
Draft
fix(common): gracefully drain leader pushes on shutdown#1440schickling wants to merge 3 commits into
schickling wants to merge 3 commits into
Conversation
Contributor
PR preview
Report historyPR 1440 · 2026-07-18 09:26 UTC
|
IGassmann
reviewed
Jul 21, 2026
IGassmann
left a comment
Collaborator
There was a problem hiding this comment.
This PR contains no changes.
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.
Problem
Orderly
Store.shutdown()can interrupt an in-flight client-to-leader push and abandon additional queued events. PR #1405 fixed that loss, but its handling of scope-finalizer order, rebase ownership, rejection recovery, and terminal failures grew too complex for this core sync path and was auto-merged before explicit human sign-off.PR #1439 reverts that implementation while retaining its stronger tests as skipped specifications. GitHub cannot literally reopen a merged PR, so this stacked draft recreates #1405 as the active design and review surface.
Goal
Keep the original problem, implementation, review history, and test discoveries available while we replace the implementation quickly with a smaller explicit pre-scope shutdown boundary tracked by #1437.
This draft is not proposed for merge in its current form.
Decisions
mainbyte-for-byte.Verification
git diff origin/main HEADis empty: this draft exactly recreates the currently merged fix(common): gracefully drain leader pushes on shutdown #1405 tree.Complexity
The current implementation adds 108 net production lines to
ClientSessionSyncProcessorand introduces rejection revision/prefix tracking, drain-failure side channels, finalizer-order coupling, and uninterruptible rebase transitions. Reducing that state and interaction budget is the purpose of reopening the design.Concerns
Friction & bottlenecks
Follow-ups
References