Quorum queues: fix resend issues after network partition #14589
Merged
Conversation
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
kjnilsson
force-pushed
the
qq-resend-issue
branch
from
9ed93f8 to
c99086a
Compare
kjnilsson
changed the title
kjnilsson
force-pushed
the
qq-resend-issue
branch
from
c99086a to
373c199
Compare
kjnilsson
force-pushed
the
qq-resend-issue
branch
from
373c199 to
da92bfd
Compare
A queue client that send a message during a network partition that later caused a distribution disconnection would in some cases never resend the lost message, even if kept in the pending buffer. Subsequent sends would be accepted by the state machine but would never be enqueued as there would be a missing sequence. In the case of publishers that use pre-settled sends the pending messages would have also been incorrectly removed from the pending map. To fix we removed timer resend aapproach and instead have the leader send leader_change messages on node up to prompt any queue clients to resend their pending buffer.
kjnilsson
force-pushed
the
qq-resend-issue
branch
from
da92bfd to
b66dc40
Compare
kjnilsson
requested review from
mkuratczyk
and removed request for
mkuratczyk
michaelklishin
approved these changes
Sep 24, 2025
Collaborator
michaelklishin
left a comment
michaelklishin
left a comment
There was a problem hiding this comment.
The Selenium suite failures are unrelated and affect (or affected, I've merged a Selenium-related PR earlier today) other branches.
michaelklishin
changed the title
michaelklishin
added a commit
that referenced
this pull request
Sep 26, 2025
Quorum queues: fix resend issues after network partition (backport #14589)
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.
A quorum queue client that send a message during a network partition
that later caused a distribution disconnection would in some cases
never resend the lost message, even if kept in the pending buffer.
Subsequent sends would be accepted by the state machine but would
never be enqueued as there would be a missing sequence.
In the case of publishers that use pre-settled sends the pending
messages would have also been incorrectly removed from the
pending map.
To fix we removed timer resend aapproach and instead have the leader
send leader_change messages on node up to prompt any queue clients
to resend their pending buffer.