[rabbitmq-discuss] 2.7.1 mirrored queues leak a lot of memory on slave nodes

Travis hcoyote at ghostar.org
Wed Feb 22 23:24:34 GMT 2012

On Wed, Feb 22, 2012 at 3:58 PM, Travis <hcoyote at ghostar.org> wrote:
> I think we're experiencing the same thing.  Previously, we were seeing
> a memory leak in 2.6.1 which was patched[1] in subsequent releases.
> Since then, we've upgraded to 2.7.1 as well and we're seeing slowly
> growing memory usage on our slaves that requires us to restart the
> slaves periodically to keep the memory usage down.
> In our case, we're using only two nodes with mirrored queues.

Also, just to show how bad the problem is, I've uploaded (to imgur) a
graph of the memory utilization to for the slave over the last few


We currently set the vm highwater mark to 10% (which ends up being
2.4GB of ram available to the system).

As you can see, we had flat memory utilization up until about week 5.
There's a small dip (where we turned things off for abit to upgrade
from 2.6.1 (with the previously mentioned patch) to 2.7.1.  After
that, memory has grown pretty steadily.  The points where it has going
almost down to zero usage after that was right after restarts of the
rabbitmq-server on this node.

Travis Campbell
travis at ghostar.org

More information about the rabbitmq-discuss mailing list