<br><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 12:29 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Scott,<br>
<div class="im"><br>
On Mon, Feb 15, 2010 at 12:24:00PM -0800, scott w wrote:<br>
> On Mon, Feb 15, 2010 at 12:03 PM, Matthew Sackman <<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>>wrote:<br>
</div><div class="im">> > They should do the same thing. This one is very odd - it looks like tcp<br>
> > listeners are being started as the Erlang VM kernel is being shutdown.<br>
> > I've never seen this before, but I'd be slightly surprised if it's<br>
> > unique to 21673. Can you reproduce this at all on the default branch?<br>
><br>
> Unfortunately no. To be honest, everything works fine on small loads. We are<br>
> using that branch for very large loads where the number of tasks don't fit<br>
> into memory. So while the problem itself may not be specific to this branch,<br>
> I haven't seen this problem in the default branch because the default can't<br>
> handle the loads we're generating.<br>
<br>
</div>Right. We have another suspicion, that you may be stopping rabbit with<br>
rabbitmqctl stop_app and then using something in /etc/init.d to start<br>
Rabbit. stop_app only stops the rabbit application running within the<br>
Erlang VM. It doesn't stop the erlang VM itself. Hence the difference<br>
between rabbitmqctl stop and rabbitmqctl stop_app. Could that be what's<br>
going on?<br></blockquote><div><br>I don't think so. I haven't been using that command on these machines. But it's possible someone else tried running that command without telling me :)<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> > Also, which version of Erlang are you running? 12B3 is the minimum for<br>
> > that branch, and 13B03 is recommended.<br>
> ><br>
><br>
> 12B-4 is what we're building from source. What benefits would we get from<br>
> upgrading to 13B03?<br>
<br>
</div>Thousands of bug fixes, and a much better GC.<br></blockquote><div><br>Great.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> Btw, are there any special rabbitmq/erlang commands or tools we can run to<br>
> verify that rabbimq is healthy beyond running rabbitmqctl and looking at<br>
> logs? I find the logs rather cryptic sometimes.<br>
<br>
</div>Generally, provided something like rabbitmqctl list_queues is<br>
responsive, all is well. If that starts taking several seconds to<br>
respond then Rabbit's under heavy load, but that doesn't mean anything's<br>
going wrong, just that it's got a lot to do.<br>
<br>
We've always written Rabbit very defensively - if it starts to go wrong,<br>
it'll explode hard, quickly. So in general, if it's up and running and<br>
doing something, then it's usually quite happy.<br></blockquote><div><br>Ok good to know.<br><br>thanks,<br>Scott<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
Matthew<br>
</font></blockquote></div><br>