[rabbitmq-discuss] Possible memory leak in the management plugin

Simon MacMullen simon at rabbitmq.com
Thu Aug 15 11:51:06 BST 2013

Note that the leak this thread was discussing was fixed in 3.1.2.

Cheers, Simon

On 15/08/13 11:46, harel at thisisglow.com wrote:
> We're seeing this happening too, though I did not think to check if the
> management plugin  was the culprit. We started using the plugin and its
> web interface around the time our rabbitmq crashes started happneing -
> all due to out of memory and being killed by the kernel.  We've disabled
> the management plugin and haven't seen the crashes yet though its too
> early to call.
> On Saturday, 15 June 2013 03:09:21 UTC+1, 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
>         short-lived 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 agent, 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.
>     https://dl.dropboxusercontent.com/u/7022167/Screenshots/n-np6obt-m9f.png
>     <https://dl.dropboxusercontent.com/u/7022167/Screenshots/n-np6obt-m9f.png>
>     https://dl.dropboxusercontent.com/u/7022167/Screenshots/an6dpup33xvx.png
>     <https://dl.dropboxusercontent.com/u/7022167/Screenshots/an6dpup33xvx.png>
>     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
>     rarely queued and most queues typically sit idle.
>     I'll be happy to provide any further diagnostic information.
>     Thanks!
> _______________________________________________
> 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