<div dir="ltr">Thanks Michael and Simon - This is immensely helpful. Just knowing some place to focus on is great. Given the nature of the issues, it appears consistent with what we've observed in our various test scenarios.<div>
<br></div><div>I've got 3.2.1 running in a different cluster for testing. Hopefully it will validate quickly and we can move to it sooner rather than later.</div><div><br></div><div>One more question - Without restarting the broker, is there any way to restart just the management agent and/or force a GC so as to clean up memory? This might buy us some time until we can upgrade.</div>
<div><br></div><div>Thanks again,</div><div><br></div><div>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 21, 2013 at 4:11 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@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="im">On 21/11/13 02:47, Matt Pietrek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The management database at 1.3GB seems excessive.<br>
</blockquote>
<br></div>
To add to what Michael said: yes, this is excessive. Almost certainly one of the leaks we've fixed since 3.0.2.<br>
<br>
As a rule of thumb I would expect the management DB to take about as much memory as Mnesia. Certainly within an order of magnitude anyway.<br>
<br>
I'm reluctant to get into tracking down exactly which old bug you are seeing :-) but there were definitely leaks in 3.0.2 such that:<br>
<br>
* Connection and channel data was never cleaned up for nodes that crashed<br>
<br>
* Consumer records might not be cleaned up<br>
<br>
* Fine stats were issued for queue slaves and never cleaned up even when the queue was deleted<br>
<br>
If you can't upgrade, in addition to the suggestions Michael made (increase the stats interval or disable the management plugin) there's a halfway house: disable fine stats collection (<a href="http://previous.rabbitmq.com/v3_0_x/management.html#fine-stats" target="_blank">http://previous.rabbitmq.com/<u></u>v3_0_x/management.html#fine-<u></u>stats</a>). This will stop you seeing message rates but will prevent some of those leaks.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, Pivotal<br>
</font></span></blockquote></div><br></div>