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

Message acknowledgement and delivery guarantees #1451

Closed
Snawoot opened this issue Jun 12, 2023 · 0 comments
Closed

Message acknowledgement and delivery guarantees #1451

Snawoot opened this issue Jun 12, 2023 · 0 comments

Comments

@Snawoot
Copy link

Snawoot commented Jun 12, 2023

Hello,

As far as I can see NSQ considers message in channel delivered as soon as it was sent to any consumer. It's consumer responsibility to make an active effort and requeue message if the message was not processed by consumer.

Here is the question. How NSQ can claim "at least once delivery" if it can effectively lose message on the edge between NSQ and consumer? It is completely possible that consumer client may crash while receiving message or TCP connection will be interrupted after message was sent to socket buffer and removed from channel. No re-queuing will happen because NSQ does not require explicit acknowledgement.

If possible, can we also have an answer to this question in FAQ?

@Snawoot Snawoot closed this as completed Jun 12, 2023
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

No branches or pull requests

1 participant