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

Matthew Sackman matthew at rabbitmq.com
Wed Jun 22 11:25:04 BST 2011

Hi Chris,

On Tue, Jun 21, 2011 at 11:18:36AM -0400, Chris Madden wrote:
>  I upgraded our erlang version to R14B03, but the LATEST.LOG still continues to be growing, albeit, more slowly perhaps? 


> I'm kind of suspicious of one of the queue usage models I'm using. When one of the processes needs to make a one-off request (rpc like), it creates a queue dedicated to that request, and expects the reply to come back on that queue. After a timeout or the response is delivered, the queue is taken down. As a result, we have queues come and go a few times a minute... not really ideal, but it helps with debugging. Beyond this, I think the rabbit setup is pretty standard. Any ideas?

How is the timeout done? Are you using our queue expiry timeout
extension or some other mechanism? This might require some mnesia
tuning, but I'm amazed if it does and you're the first person to run
into this - it's such a common scenario I'm sure we'd have heard about
it earlier.


More information about the rabbitmq-discuss mailing list