[rabbitmq-discuss] Possible memory leak in the management plugin
simon at rabbitmq.com
Mon Jun 17 16:32:28 BST 2013
On 17/06/13 15:45, Travis Mehlinger wrote:
> Hi Simon,
> Thanks for getting back to me. I'll need to restart our monitor and give
> it some time to leak the memory. I'll let you know the results sometime
> later today.
> One thing I failed to mention in my initial report: whenever we
> restarted one of our services, the queues they were using would get
> cleaned up (we have them set to auto-delete) and redeclared. Whenever we
> did that, we would see the memory consumption of the management DB fall
> off sharply before starting to rise again.
That is presumably because the historical data the management plugin has
been retaining for those queues got thrown away. If you don't want to
retain this data at all, change the configuration as documented here:
However, I (currently) don't believe it's this historical data you are
seeing as "leaking" since making queries should not cause any more of it
to be retained.
> Let me know if you'd like any further information in the meantime.
> Best, Travis
> On Mon, Jun 17, 2013 at 6:39 AM, Simon MacMullen <simon at rabbitmq.com
> <mailto:simon at rabbitmq.com>> wrote:
> Hi. Thanks for the report.
> My first guess is that garbage collection for the management DB
> process is happening too slowly. Can you invoke:
> $ rabbitmqctl eval
> and post the results?
> Cheers, Simon
> On 15/06/13 03:09, Travis Mehlinger wrote:
> We recently upgraded RabbitMQ from 3.0.4 to 3.1.1 after noticing
> two bug
> fixes in 3.1.0 related to our RabbitMQ deployment:
> * 25524 fix memory leak in mirror queue slave with many
> publishing channel
> * 25290 fix per-queue memory leak recording stats for mirror
> queue slaves
> However, in our case, it seems that the management plugin may
> still have
> a memory leak. We have a monitoring agent that hits the REST API to
> gather information about the broker (number of queues, queue depth,
> etc.). With the monitoring agent running and making requests
> against the
> API, memory consumption steadily increased; when we stopped the
> memory consumption in the management plugin leveled off.
> Here a couple graphs detailing memory consumption in the broker (the
> figures are parsed from rabbitmqctl report). The first graph
> shows the
> ebb and flow of memory consumption in a number of components and the
> second shows just consumption by the management plugin. You can see
> pretty clearly where we stopped the monitoring agent at 1:20.
> We have two clustered brokers, both running RabbitMQ 3.1.1 on Erlang
> R14B-04.1. There are typically around 200 queues, about 20 of
> which are
> mirrored. There are generally about 200 consumers. Messages are
> queued and most queues typically sit idle.
> I'll be happy to provide any further diagnostic information.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.__rabbitmq.com
> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
> Simon MacMullen
> RabbitMQ, Pivotal
More information about the rabbitmq-discuss