Skip to content
Discussion options

You must be logged in to vote

Update: the fix is ready for review.

The PR ignores REPLICATED_SUBSCRIPTION_UPDATE markers for __compaction in ReplicatedSubscriptionsController.receiveSubscriptionUpdated. The compactor owns this cursor, so a remote update can never be applied to it. The check is on the receiving side, so it also clears markers that are already in the backlog of a stuck cluster. It also stops a remote update from creating __compaction as an ordinary replicated subscription on a cluster that has no compaction subscription yet.

Feedback from the maintainers is welcome, also about a backport to branch-4.0.

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@lhotari
Comment options

lhotari Oct 21, 2026
Collaborator

Answer selected by lhotari
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants