[rabbitmq-discuss] cluster memory alarm blocks producer too long

Matthias Radestock matthias at rabbitmq.com
Thu Jun 27 07:52:01 BST 2013

On 20/06/13 04:52, richmonkey wrote:
> slave:
>   {memory,
>       [{total,3345436680},
>        {queue_procs,2660479408},
>  {vm_memory_limit,3301285888},
> master:
>   {memory,
>       [{total,1523362624},
>        {queue_procs,1318303888},
>   {vm_memory_limit,3301285888},

So the memory is being used by the queues, which is to be expected. It 
is also not surprising to, generally, see higher memory consumption at 
the slave, due to the way mirrored queues are implemented. However, just 
like the master, the slave should be paging messages to disk to free up 
memory. The slave may have to page a bit more than the master, but not 
to the degree that would cause the massive difference in memory alarm 

Please post

1) the output of 'rabbitmqctl report' when the slave has been in the 
memory alarm state for a while

2) code that may allow us to reproduce the problem



More information about the rabbitmq-discuss mailing list