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

Simon MacMullen simon at rabbitmq.com
Wed Jun 19 11:01:13 BST 2013


What does "rabbitmqctl status" / management node details page say the 
memory is used by?

Cheers, Simon

On 19/06/13 06:16, Xuehua Hou wrote:
> Hi,
> I'm testing rabbitmq cluster.
> The problem same as
> https://groups.google.com/forum/?fromgroups#!searchin/rabbitmq-discuss/memory$20cluster/rabbitmq-discuss/85g_ScoeeJM/jMspuiJHD7sJ
> still exists.
> I can reproduce the issue.
>
> I runned rabbitmq-server-3.1.1 on two centos6 machines, the erlang
> version is R16B.
> The two machines are 4 core and 8G ram.
> I used mirrored durable queue for HA.
> Two nodes are disc.
>
> Reproduce step:
> 1.start four producers  and publish a lot of messages(more than 1000000).
> 2.start four consumers
> Producers and consumers running more than one hour, memory alarm will go
> off.
> The master memory slow down quickly,
> But the slave node stay in memory alarm state too long(more than 10 min).
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


-- 
Simon MacMullen
RabbitMQ, Pivotal


More information about the rabbitmq-discuss mailing list