Yes, I'll set this up on a test server and see what happens.� I just wanted to check first and see if it was a known problem.<br><br>Thanks,<br><br>Andrew<br><br><div class="gmail_quote">On Wed, Nov 30, 2011 at 6:42 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Andrew,<br>
<br>
On 30/11/11 03:46, Andrew Maizels wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2.7 seems to ignore TTL limits.<br>
</blockquote>
<br>
TTLs in 2.7 certainly can't be broken completely; we have tests that check that.<br>
<br>
In fact they should work *better* in 2.7 in that requeued messages retain their original TTL rather than getting a fresh one.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
We had a slow �consumer leave about 1.8 million 40KB messages on the<br>
queue, which filled up the available disk and brought RabbitMQ down.<br></div><div class="im">
The queues are durable and bound to a single exchange; no special<br>
parameters apart from the TTL, which is typically 600000<br>
milliseconds.<br>
</div></blockquote>
<br>
Were these 1.8 million messages the result of a relatively steady inbound stream? Over what period of time?<br>
<br>
Can a single message get routed to multiple queues?<br>
<br>
What memory limit does rabbit think it has (check the log for an entry like:<br>
=INFO REPORT==== 28-Nov-2011::12:14:40 ===<br>
Memory limit set to 4815MB of 12037MB total.<br>
)?<br>
<br>
Do you still have the log files from the time it failed?<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We've reverted to 2.6.1 for now, and everything is working again.<br>
</blockquote>
<br></div>
Is there any chance you could go back to 2.7.0, perhaps in a test setup, and see whether you can replicate the problem? If you do then taking a snapshot of the database dir at the time, together with the output of 'rabbitmqctl report' should give us enough data to figure out what's going wrong.<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Ahh... We are all heroes; you and Boo and I.<br>Hamsters and rangers everywhere, rejoice!<br>Read Peopleware! <a href="http://www.amazon.com/Peopleware-Productive-Projects-Teams-Second/dp/0932633439" target="_blank">http://www.amazon.com/Peopleware-Productive-Projects-Teams-Second/dp/0932633439</a><br>
<br>