Hi Simon,<div><br></div><div>You meant the cluster not only stop all publish requests and will crash at the end? Means consume requests also can't be send to the RabbitMQ? </div><div><br><div>Regards,</div><div>Wong<br>
<br><div class="gmail_quote">On Wed, Oct 24, 2012 at 5:14 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@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><div>On 24/10/12 07:46, Wong Kam Hoong wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi RabbitMQ Team,<br>
<br>
If one of the RabbitMQ node under cluster environment facing out of disk<br>
space problem, what will happen?<br>
<br>
1) The cluster stop function properly or even worst?<br>
2) Just impacted node stop sync data from others?<br>
</blockquote>
<br></div></div>
Disc space monitoring was added in 2.8.2. If the disc space falls below the monitored threshold then *the whole cluster* will stop accepting publishes until more space becomes available.<br>
<br>
This doesn't completely stop you from running out of disc space, but it makes it very unlikely that RabbitMQ will take the last disc space on the machine.<br>
<br>
Running out of disc space will cause RabbitMQ to crash.<br>
<br>
Cheers, Simon<span><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div></div>