[IMPROVED] Interest desync after consumer create/update#7440
Merged
neilalexander merged 1 commit intomainfrom Oct 19, 2025
Merged
[IMPROVED] Interest desync after consumer create/update#7440neilalexander merged 1 commit intomainfrom
neilalexander merged 1 commit intomainfrom
Conversation
Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
neilalexander
added a commit
that referenced
this pull request
Oct 30, 2025
neilalexander
added a commit
that referenced
this pull request
Nov 12, 2025
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
2 participants
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.
Due to
noInterestbeing determined on individual servers and not only by the leader, this means the stream can desync if a consumer is created or updated such that new interest on published subjects is established at different logical times.This race condition happens due to the published messages going over the stream layer, whereas consumer creates and updates go over the meta layer. Slower meta layer applies or differing network latencies could then result in "no interest" being marked differently on different servers.
The fix introduced in this PR can be included in a patch version. The desync will still occur, but individual servers can now recognize this and remove messages at the start of the stream that have no interest. But, technically this does not solve the core issue of the ordering differences between the meta and stream layer. There can be multiple ways to solve that, but will likely need to wait for 2.14+. If the consumer assignments are managed by the stream, and those assignments go over the stream layer, then this would be a better way to ensure consistency without needing to fix things up later.
Signed-off-by: Maurice van Veen github@mauricevanveen.com