[rabbitmq-discuss] broken release?

[Simon MacMullen]

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:

http://www.rabbitmq.com/memory.html#diskfreesup

...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