[rabbitmq-discuss] Possible memory leak?

David King dking at ketralnis.com
Sat Jul 3 19:13:08 BST 2010

> If you just let it run, what happens?

I don't know. I guess we can see, but my guess is that it will wake me up at two in the morning to fix the site. That's what usually happens when rabbit crashes, anyway.

> The default Erlang gc performs garbage collections after a certain number of reductions, and that number is so high that a queue process which does work infrequently may not perform a gc for a very long time indeed. That's particularly noticeable when the message sizes are large. What's the average and max message size in your set up?

They're just IDs, so they'll be between 5 and 10 bytes each.

>> So to be clear, we have 13
>> queues that all sit at 0 backlog basically all of the time. Certainly
>> no queues that grow at the same rate our memory does. 
> How are you measuring the queue length? With 'rabbitmqctl list_queues'?


> Are any of the other items which can be listed with rabbitmqctl - exchanges, bindings, connections, channels, consumers - growing?

That doesn't appear to be true, no

> Also, have you installed any plug-ins?


More information about the rabbitmq-discuss mailing list