On Wed, Feb 22, 2012 at 3:58 PM, Travis 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

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 11 | next ›
Discussion Overview
grouprabbitmq-discuss @
postedFeb 22, '12 at 8:12p
activeMar 12, '12 at 5:08p



site design / logo © 2022 Grokbase