[rabbitmq-discuss] LATEST.LOG growth on clustered ram node

Chris Madden chris.madden at gmail.com
Mon Jun 20 23:24:45 BST 2011

I'm working on a system that currently has 2 rabbit nodes in a cluster. Ideally, one would be a disc node and one would be a ram node. The two nodes exist on individual machines on the same LAN segment. The ram node is on a machine that can come and go every now and again. Network connectivity between the nodes is solid.

On each machine, applications wishing to use rabbit talk to the local instance, secure in the knowledge that rabbit will get the data where it needs to go. I've a modest number of exchanges (say, 5ish), and a mix of long-lived and short-lived queues. There is a modest flow of messages (say, maybe 30-40 a minute, amounting to a couple meg at peak).

In a nutshell, the LATEST.LOG file on my ram clustered node grows, by all accounts, forever. I left it running over the weekend and it was well over 500meg. In the past I've let it run until it consumed all the space on the partition and the broker instance cratered. Running it as a ram node instead of a disc node obviates the problem, but is sub-optimal.

I'm using rabbit 2.5.0, though I've seen the problem on 2.4.0 and 2.4.1. The OS is linux based (2.6.32), and our Erlang version is R14A.

The googles (or my google-fu) seem to be silent beyond tweaking mnesia parameters that I don't fully understand. Any insight or assistance would be greatly appreciated! 



More information about the rabbitmq-discuss mailing list