[rabbitmq-discuss] Consumer crash, redelivery and prefetch
riccardi at systran.fr
Thu Mar 13 19:31:02 GMT 2014
Consumer crash, redelivery and prefetch
I'm having issues with consumer crash, redelivery and prefetch:
The messages ack strategy I've chosen is to ack the message only after
the consumer has finished working on the message. I need this because I
cannot aford any lost message, even in case of consumer crash during the
work on the message.
For performance reason my consumer have a non 0 prefetch, so when my
consumer is handling a message (doing some work related to the message),
other messages are pushed to the client so that it has them already
available when it's done working on the previous message.
With this, when a message makes the consumer crash, the handled message
*and* the prefetched ones are re-queued, with the flag "redelivered" ==
I currently have no other choice than rejecting all messages that have
the "redelivered" flag set to true, because I have no way to distinguish
the message that cause the crash from the prefetched ones that did
Indeed if I retry to work on a redelivered message, the consumer will
crash again on the poison message, in an infinite loop. However I would
like to not reject the previously prefetched messages since they are
This reasoning also applies to transient crashes that are not
systematically reproduced by the message.
Ideally the solution would be to be able to distinguish the first non
ack'd message from the other ones when the consumer crashes, or
alternatively having two types of ack : one "I'm starting to work on
this message", and a second one "I've finished working on this message".
Otherwise a redelivery count would do the trick (even if it means
working multiple times on a message that did make the consumer crash,
which is not efficient if we know crashes happen mostly systematically).
The redelivery count is a "planned" feature according to
http://www.rabbitmq.com/specification.html, but when will it be really
Having a parameter per queue like the TTL to tell a maximum redelivery
count before dead lettering the message would be much helpful in my case
(a RPC above rabbitmq, which is probably not a highly specific and rare
More information about the rabbitmq-discuss