<div dir="ltr">All queues are empty and "rabbitmqctl list_queues name memory" shows they use about 3K each.<div>VM memory stats are much lower then the one shown in the overview.</div><div>We're using 2.8.1 - I'll try upgrading to 2.8.7<br clear="all">
<div dir="ltr"><div><br></div><div>Thanks<br clear="all"><div dir="ltr"><i style="color:rgb(102,102,102)">--</i><span style="color:rgb(102,102,102)">Raviv</span></div></div><div><font color="#666666"><i><br></i></font></div>
</div><br>
<br><br><div class="gmail_quote">On Thu, Oct 4, 2012 at 4:57 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">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">
<div class="HOEnZb"><div class="h5">On 04/10/12 15:53, Simon MacMullen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 04/10/12 13:01, Raviv Pavel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Based on the management UI, memory usage doesn't drop and publishers are<br>
still blocked.<br>
</blockquote>
<br>
Hmm. In that case my first guess would be that the queue you deleted /<br>
purged wasn't the queue which was using all the memory. Check the memory<br>
use of other queues - this can be found on the queue details page, or<br>
with "rabbitmqctl list_queues name memory". Also, check the VM-wide<br>
memory statistics (on the node details page, under "advanced". This<br>
might give a clue as to where the memory is going.<br>
</blockquote>
<br></div></div>
...and please make sure you are running the latest version of RabbitMQ (2.8.7, atm), since we have fixed a few memory leaks in the in recent versions.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div></div>