[rabbitmq-discuss] Delivery / Redelivery counter plugin

Emile Joubert emile at rabbitmq.com
Wed Nov 13 12:18:51 GMT 2013


On 13/11/13 11:55, Karl Nilsson wrote:

> I know there is a planned feature for this (basic / deliver / 01) but I
> checked with Alvaro who has confirmed it isn't a priority at this time
> so we could do with some kind of half-way house in the meantime.

The priority of this feature has just raised because it is determined in
part by demand.

The complete implementation of toxic message handling is complicated by
the need for on-disk representations to change in order to accommodate
the counter information. Maintaining the counter in RAM is not an option
since the redelivery information could be unbounded.

This feature would need to modify and interact with multiple broker
subsystems, so not the ideal for a plugin.

The best alternative at present is to use the redelivery flag as an
indicator that a message may be suspect. It is possible to extend the
utility of the redelivery flag slightly by republishing redelivered
messages to a separate queue for high-risk messages. If messages from
the high-disk queue again have the redelivery flag set then the message
is probably toxic and should be handled as an exception.


More information about the rabbitmq-discuss mailing list