[rabbitmq-discuss] Memory watermark alert not resetting.
simon at rabbitmq.com
Thu Oct 4 15:53:24 BST 2012
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.
More information about the rabbitmq-discuss