[rabbitmq-discuss] Memory watermark alert not resetting.

[Matthias Radestock]

On 04/10/12 15:53, Simon MacMullen wrote:
> On 04/10/12 13:01, Raviv Pavel wrote:
>> Based on the management UI, memory usage doesn't drop and publishers are
>> still blocked.
>
> Hmm. In that case my first guess would be that the queue you deleted /
> purged wasn't the queue which was using all the memory. Check the memory
> use of other queues - this can be found on the queue details page, or
> with "rabbitmqctl list_queues name memory". Also, check the VM-wide
> memory statistics (on the node details page, under "advanced". This
> might give a clue as to where the memory is going.

...and please make sure you are running the latest version of RabbitMQ 
(2.8.7, atm), since we have fixed a few memory leaks in the in recent 
versions.

Matthias.