[rabbitmq-discuss] Simple benchmark and results
matthias at lshift.net
Thu Oct 22 09:58:12 BST 2009
Sylvain Hellegouarch wrote:
> I assume this means that if the consumer fails at processing correctly
> the message it won't see it again right, whereas with an ack by the
> consumer, one can ensure consistency if the processing fails before the
> ack call.
Sort of. In auto-ack/no-ack mode the broker forgets about the message as
soon as it has sent it. So any failure of the broker, network or
consuming client after the sending will result in the message being
lost. By contrast, when acks are enabled the broker only forgets about a
message when the client has sent it an ack. Any failure before then
results in an eventual retransmit.
More information about the rabbitmq-discuss