[rabbitmq-discuss] Memory leak when using shovels?

Travis hcoyote at ghostar.org
Fri Dec 30 18:59:32 GMT 2011

On Tue, Dec 20, 2011 at 1:20 PM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
>> We're seeing a slow leak that grows over 6-8 days on a few instances of
>> rabbitmq that are using the shovel plugin and we're not exactly sure
>> why.  I'm not sure if this is related to the memory leak we previously
>> reported a few weeks ago that was fixed in 2.7.1
> Is the shovel publishing to mirrored queues? If so then then it's probably
> the same problem.

It is.

I upgraded to a patched version of 2.6.1 that has the fix y'all
created, but I'm still seeing a slow increase of memory usage for no
apparent reason.

> Two observations:
> 1) there is a stray 'queue.declare' in the first shovel config. This will
> cause a new queue to be created every time the shovel connection is
> interrupted. You would surely have seen those queues in the management UI
> and rabbitmqctl, so I doubt that's the cause of the leak.

Would this be seen as queues named amqp.gen-<randomname>?  We've been
plagued by those and I never could figure out why.

> 2) Instead of the establishing a connection to 'localhost', specify no host
> at all, e.g.
> "amqp://my-user-prod@/my-prod"; that way a more efficient and less fault
> prone direct connection is used instead of a network connection (which is
> also why no password is required).

Interesting.  Thanks!

Travis Campbell
travis at ghostar.org

More information about the rabbitmq-discuss mailing list