[rabbitmq-discuss] Occasional slow message on a local machine

Matthias Radestock matthias at rabbitmq.com
Fri Sep 14 22:32:55 BST 2012


On 14/09/12 21:07, Brennan Sellner wrote:
> It appears that cleaning up a queue (e.g. auto-delete on channel
> close) requires Rabbit to fsync, even if the queue is non-durable.

Confirmed. That is certainly unexpected, so I have filed a bug.

What appears to be happening is that we attempt to remove the entries
for the queue from the durable queue and binding tables. Even though
there are no such entries mnesia still writes to its disk log, which we 
subsequently detect and request an fsync.

Looks like we need to get smarter here.

> So.  The question is: is it possible to declare a queue that's
> entirely transitory, and doesn't result in Rabbit having to hit the
> disk at any point in the queue's life cycle?

Apparently not.

> It really seems like there should be *some* way to have a
> lightweight, ephemeral queue...


Thanks for your help in tracking this down.



More information about the rabbitmq-discuss mailing list