Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IMPROVED] Clustering: queue redelivery to different members #1214

Merged
merged 1 commit into from
Oct 15, 2021

Conversation

kozlovic
Copy link
Member

Until now, queue redeliveries in cluster mode behaved differently
than in standalone/FT mode. That is, messages delivered to a
queue member were always redelivered to that same member.
This could be a problem if the application hosting the queue
member had an issue where it would not acknowledge messages
but at the same time was still running. The leader would always
redeliver those same unacknowledged messages to that same
misbehaving client. With this change, the queue redelivery is
now the same regardless of the streaming server running mode.

Signed-off-by: Ivan Kozlovic ivan@synadia.com

Until now, queue redeliveries in cluster mode behaved differently
than in standalone/FT mode. That is, messages delivered to a
queue member were always redelivered to that same member.
This could be a problem if the application hosting the queue
member had an issue where it would not acknowledge messages
but at the same time was still running. The leader would always
redeliver those same unacknowledged messages to that same
misbehaving client. With this change, the queue redelivery is
now the same regardless of the streaming server running mode.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
@kozlovic
Copy link
Member Author

Thanks to @mihai-tiriplica-f3 for verifying that this change works well and solves issues when an application uses a queue subscription but for some reason does not acknowledge the messages. With this change, at least those messages will be redelivered to other healthy members at one point.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.06%) to 91.531% when pulling 771feb5 on clustering_queue_redelivery_changes into e06a494 on main.

Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kozlovic kozlovic merged commit 3b51bc9 into main Oct 15, 2021
@kozlovic kozlovic deleted the clustering_queue_redelivery_changes branch October 15, 2021 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants