[FIXED] R1 mset.lseq desync when exceeding limits#7658
Merged
neilalexander merged 1 commit intomainfrom Dec 17, 2025
Merged
Conversation
MauriceVanVeen
force-pushed
the
maurice/mset-lseq-desync
branch
from
9b97d67 to
36ffbc6
Compare
Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
MauriceVanVeen
force-pushed
the
maurice/mset-lseq-desync
branch
from
36ffbc6 to
549711a
Compare
This was referenced Jan 6, 2026
neilalexander
added a commit
that referenced
this pull request
Jan 6, 2026
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.
mset.lseqis incremented for every successful call toprocessJetStreamMsgthat results in storing a message. However, this wasn't fully true. An invalid TTL header or (more commonly) exceeding resource limits would seemset.lseqpre-incremented and not reset after an error. Normally this would not result in an error, but the stream can't scale up cleanly when in this state, resulting inErrSequenceMismatch.Signed-off-by: Maurice van Veen github@mauricevanveen.com