[rabbitmq-discuss] Message TTL working fine in 2.6.1, broken in 2.7.0?

Andrew Maizels andrew.maizels at gmail.com
Wed Nov 30 03:46:08 GMT 2011


We push about 1TB of data through RabbitMQ per day, and we use TTL-limited
queues extensively to prevent slow/dead consumers from taking out the
server.  While we had some hiccups with 2.5, this has been completely
reliable since we upgraded to 2.6.

2.7, on the other hand, seems to ignore TTL limits.  We had a slow consumer
leave about 1.8 million 40KB messages on the queue, which filled up the
available disk and brought RabbitMQ down.

We've reverted to 2.6.1 for now, and everything is working again.

Has anyone else experienced this?  Is there anything we need to configure
in 2.7 to make TTL work as expected, or is this a bug?

The queues are durable and bound to a single exchange; no special
parameters apart from the TTL, which is typically 600000 milliseconds.


Andrew Maizels
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111130/cba7057e/attachment.htm>

More information about the rabbitmq-discuss mailing list