[rabbitmq-discuss] Node reaches RAM High Watermark quickly

[Chris Larsen]

Hello, we're running a bunch of nodes of RabbitMQ 2.3.1 on Erlang R13B03
under Debian and one of the nodes has a problem where it reaches the high
watermark, stops accepting producers and requires a reboot to recover. The
consumers eat all of the messages so that the queues are empty but the used
Ram never drops. I checked for queue leakage and we only have 9 queues
defined with about 100 unacked messages in one queue when the ram fills up.
We only have about 30 connections and less than 20 channels shown in the GUI
when it fails. The system isn't running in swap and messages are sometimes a
couple of MB in size but no larger. Any ideas what it might be? Thank you!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110912/e1ef2cc7/attachment.htm>