<br><br><div class="gmail_quote">On Wed, Sep 16, 2009 at 4:48 AM, majek04 <span dir="ltr"><<a href="mailto:majek04@gmail.com">majek04@gmail.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 Tue, Sep 15, 2009 at 17:03, Suhail Doshi <<a href="mailto:suhail@mixpanel.com">suhail@mixpanel.com</a>> wrote:<br>
> Doing some investigation into what happened, apparently the memory just<br>
> instantly got used, it wasn't leaking something slowly...any ideas?<br>
> Attached is an image of memory usage, then the consumer dies freeing up the<br>
> memory used later.<br>
<br>
</div>It looks like erlang was trying to allocate 5 gigs of RAM, and failed.<br>
This could have happened during garbage collection, but only<br>
if a single erlang process was using all the memory.<br>
<br>
Do you have a single large queue?<br></blockquote><div><br></div><div>Yes just 1 queue, definitely adds up after a while if consumers are not running</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Are you sure that the queue had reasonable size during the crash?<br></blockquote><div><br></div><div>I am not sure</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Maybe all the consumers had died and rabbit just ran out of memory?<br>
<br></blockquote><div><br></div><div>No the consumers were very alive.</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Cheers!<br>
�Marek Majkowski<br>
</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>