[rabbitmq-discuss] TTLs in 2.5.1

Aaron Westendorf aaron at agoragames.com
Tue Dec 20 03:29:09 GMT 2011

We're running Rabbit 2.5.1 in a 2 node cluster and need  to implement
message TTLs to mitigate some pressing problems. If anyone could help
us out with some questions we have that would be most appreciated.

Are they fully supported in this version?
If we're going to enable TTLs, is there a pressing need to upgrade or
can we stay on 2.5.1?
Is there anything special to note about them in a 2.5.1 cluster?
Do we need to turn on client qos, or will rabbit change its consumer
delivery rules on TTL'd messages?
Are there any recommended lower bounds on this value?
What kind of effect should we expect message TTL to have on resource
Will this significantly impact the memory footprint specifically?
Anything special about TTL in the case where rabbit is already under
very high load?

Sorry for all the specific questions, we just want to make sure that
if we "do it live" that we'll see the result we're expecting. For the
most part we have memory usage running in the 20-30% of memory alarm
range, but it can climb quickly in cases where we want TTL to work the
hardest for us and we're at thousands of msgs/sec. We're looking at
timeouts in the 5-10sec range or so, maybe as low as 2sec, which could
translate to 10-20k timeouts/sec in worst-case scenarios. We've seen
up to 16 MB/sec disk writes on our rabbit hosts, presumably all from
rabbit queue paging and during said worst-cases, for an idea of the
kind of volume that could back up with something goes awry and we want
messages to die off fast.


Aaron Westendorf
Senior Software Engineer
Agora Games
359 Broadway
Troy, NY 12180
Phone: 518.268.1000
aaron at agoragames.com

More information about the rabbitmq-discuss mailing list