[rabbitmq-discuss] major failure when clearing large queue backlog

Matthew Sackman matthew at rabbitmq.com
Tue Aug 16 11:35:30 BST 2011

On Mon, Aug 15, 2011 at 01:29:23PM -0400, Aaron Westendorf wrote:
> I can email you logs, but they're really not exciting. It's all just noise
> as messages were published and consumers had yet to initialize and declare
> exchanges, queues and bindings.

Hmm, that's a pity.

> I assume you have tests for spooling to disk when rabbit is low on memory.
> Has this been tested in a cluster situation such as I described?

Part of our test suite certainly does simulate low memory conditions.

> I checked our configurations, and I wonder if this is what caused the
> problem:
> [{rabbit, [{vm_memory_high_watermark, 0}, {cluster_nodes,
> ['artemis','hermes']}]}].

Erm, setting that to 0 disables the memory monitor, which then forces
Rabbit to default to thinking that there's probably about 1GB RAM
installed. This is very certainly not what you want. I'd set that back
to the default of 0.4 and see how you get on with that.


More information about the rabbitmq-discuss mailing list