Hi Matthias,<div><br></div><div>Besides of stop all publishes, how about consumes? Does RabbitMQ stop the consumes as well?</div><div><br></div><div>Regards,</div><div>Wong<br><br><br><div class="gmail_quote">On Wed, Oct 24, 2012 at 5:34 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@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 24/10/12 10:14, Simon MacMullen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the disc space falls below the monitored threshold then *the whole<br>
cluster* will stop accepting publishes until more space becomes<br>
available.<br>
</blockquote>
<br></div>
The same is true for memory alarms, i.e. when *any* node in a cluster encounters a memory alarm then *all* nodes will block publishers.<br>
<br>
Matthias.<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</blockquote></div><br></div>