[rabbitmq-discuss] broken release?

Simon MacMullen simon at rabbitmq.com
Thu May 3 10:42:22 BST 2012

On 03/05/12 10:15, Matthias Radestock wrote:
> i.e. there is insufficient disk space and therefore publishing
> connections are probably being blocked.

To add to this: 2.8.2 introduced disk space monitoring. By default 
RabbitMQ will refuse to accept messages when (free disc space) < 
(physical memory). You can change this behaviour following instructions at:


...but you should be aware that this feature is there for a reason - 
under heavy load a RabbitMQ server can page all its messages out to 
disc. If doing this exhausts disc space, bad things will happen.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list