The memory leak is in the consumers, thanks Matthias.<div><br></div><div>Suhail<br><br><div class="gmail_quote">On Thu, Jul 30, 2009 at 4:37 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Suhail,<div class="im"><br>
<br>
Suhail Doshi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yeah definitely has to be, the moment I kill it the memory drops back down and it is gradually growing, you can even see it gradually growing in the images.<br>
</blockquote>
<br></div>
Do you definitely see the rabbit process consuming the memory? How big does it get? And what about CPU usage?<br>
<br>
The reason I am asking is that killing the server also affects the clients, i.e. it is possible that a *client* is consuming all the memory, and releases it as soon as the server connection is severed.<br>
<br>
So please check the *per-process* memory and CPU stats.<br>
<br>
Now, if it really is the server that is eating the memory, please run all the various list_* commands in rabbitmqctl to see whether any of them are showing growth.<br>
<br>
Finally, try publishing messages without marking them as persistent, and see whether that changes the behaviour.<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><a href="http://mixpanel.com">http://mixpanel.com</a><br>Blog: <a href="http://blog.mixpanel.com">http://blog.mixpanel.com</a><br>
</div>