We've decided to just move the processing that happens on that box to another server, and leave the HA pair dedicated to being<div>a rabbitmq cluster.</div><div><br></div><div>If it happens again though, I'll test this out.</div>
<div><br></div><div>-allan</div><div><br><br><div class="gmail_quote">On Tue, Mar 2, 2010 at 4:26 AM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</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, Mar 02, 2010 at 12:19:29PM +0000, Matthew Sackman wrote:<br>
> Obviously, this'll require building from source...<br>
<br>
</div>Actually, you shouldn't need that patch - it would seem that the<br>
parameters -kernel net_ticktime 500 should do the same. If you put in<br>
your rabbitmq.conf file (which under linux should live in<br>
/etc/rabbitmq/rabbitmq.conf):<br>
<br>
SERVER_START_ARGS="-kernel net_ticktime 500"<br>
<br>
Then you should find that works as well as the patch (and doesn't<br>
require building from source).<br>
<div><div></div><div class="h5"><br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>