[rabbitmq-discuss] Growing Memory Use and Queues

Emile Joubert emile at rabbitmq.com
Thu Jun 13 09:37:47 BST 2013


On 12/06/13 12:40, harel at thisisglow.com wrote:
> We're seeing this recently since upgrading to the 3.x version of rabbit. 

Can you reproduce the problem on the latest version?

> We are running about 25 queues and all is good for a while. But
> sometimes rabbit crashes hard with out of memory errors even if the
> queues are not noticeably larger or busier than usual.
The broker can run out of memory for other reasons, e.g. if you create a
very large number of channels. The output of "rabbitmqctl report" can
help to identify such cases. You can send the output to the list (or to
me privately if it is too large) if you need help interpreting it.

Recent versions of the management plugin can also show memory usage
breakdown in the node overview page.

If this does not pinpoint the cause then make sure there is no other
service on the same server as the broker that takes alot of RAM.

> I have a 3.2GB crash dump which honestly I don't even know how to
> begin looking at. 

Crash dump files rarely contain anything useful. Yours probably says
"Failure to allocate some bytes". The broker log and sasl log are
usually more useful. I would expect to see memory alarms in the broker log.


More information about the rabbitmq-discuss mailing list