(2.12) [FIXED] Remove recovered streams/consumers if not in catchup meta snapshot#7824
Merged
neilalexander merged 1 commit intomainfrom Feb 13, 2026
Merged
(2.12) [FIXED] Remove recovered streams/consumers if not in catchup meta snapshot#7824neilalexander merged 1 commit intomainfrom
neilalexander merged 1 commit intomainfrom
Conversation
…eta snapshot Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
MauriceVanVeen
force-pushed
the
maurice/rm-recovered
branch
from
a75f8e3 to
60b16f0
Compare
neilalexander
added a commit
that referenced
this pull request
Feb 17, 2026
Follow-up of #7824. Aligning and simplifying the cleanup of orphaned streams and consumers with `checkForOrphans`. Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
neilalexander
added a commit
that referenced
this pull request
Feb 20, 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.
TestJetStreamClusterDeleteConsumerWhileServerDown(and others) would fail if the restarted server couldn't install a snapshot during shutdown. This happened if the server was a follower of the meta layer and committed the consumer create from a heartbeat, which isn't stored in the log. So, when the server restarted it didn't know it could commit/apply this consumer create again (since it already did so prior to restart). Then, when the meta snapshot was received to catch this server up, it would not properly remove the consumer as it wasn't tracked in its assignments.Marked as 2.12+ as #7540 is only cherry-picked there.
Signed-off-by: Maurice van Veen github@mauricevanveen.com