[FIXED] Durable subscriptions miss messages after cluster restart #591
Conversation
This file contains 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
If a durable subscription (can apply to durable queues too) is created with a start position other than SequenceStart, and this subscription receive some messages, then is closed. At that time either more messages are sent or there were already more messages in the channel, then after a cluster restart (all nodes are restarted), then when the durable (queue) is resumed, it would seem to not receive any messages in the channel. Only new messages produced after the cluster is restarted would be delivered. Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
kozlovic
force-pushed
the
fix_cluster_sub_start_seq
branch
from
dc71b27
to
d022f0c
Compare
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.
If a durable subscription (can apply to durable queues too) is
created with a start position other than SequenceStart, and this
subscription receive some messages, then is closed. At that time
either more messages are sent or there were already more messages
in the channel, then after a cluster restart (all nodes are
restarted), then when the durable (queue) is resumed, it would
seem to not receive any messages in the channel. Only new messages
produced after the cluster is restarted would be delivered.
Signed-off-by: Ivan Kozlovic ivan@synadia.com