[rabbitmq-discuss] Memory leak caused by error_logger in 2.8.6?

Simon MacMullen simon at rabbitmq.com
Tue Oct 23 18:10:33 BST 2012

On 23/10/12 17:39, Travis wrote:
> On Tue, Oct 23, 2012 at 4:18 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
>> Hmm.
>> Looks like it is progressing too slowly towards GC; what happens if you GC
>> it manually?
> I'm not sure how to force a manual GC.  I'd be happy to test it out if
> you can tell me how.

Ah right, I saw an Erlang term in your mail and assumed you were an 
Erlang developer :-) Try:

rabbitmqctl eval 'erlang:garbage_collect(whereis(error_logger)).'

And from another mail:

> Our best guess is that when the shovels undergo a period where they
> have network issues while talking to the cluster, they start spamming
> the logs with output and the memory usage rises.  Once the network
> connectivity issues resolve themselves, the memory usage seems to
> stabilize and remain moderately flat.

That makes sense - during the outage the error logger does a lot of work 
but doesn't get quite as far as GCing, then after the outage is over it 
does so much less work that it never goes through enough reductions to GC.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list