[rabbitmq-discuss] beam process using 100% cpu and lots of memory

[Joel Heenan]

We are having a situation where when we put lots of data through a
RabbitMQ queue we sometimes we see a beam process running using 100%
cpu and up to 1.5GB (RSS) of memory. The only way to resolve this
situation is to restart RabbitMQ.

We are trying to trace down the exact conditions that cause the
problem, and I hope to also post up an strace and lsof of what it is
doing during this time and log messages.

I could not find anything particularly interesting in the rabbitmq.log file.

We are talking a very large number of connections here, 1807334
connections in 17 hours, or 29/second.

We started using RabbitMQ Stomp Server 1.6.0-5 then moved to version
latest public umbrella (as of 24 hours ago). OS is Centos 5.4 x86_64
Xen domU with 4GB of RAM and 1VCPU.

We are using persistent mode on the queues, currently testing with
non-persistent.

Joel