[rabbitmq-discuss] General approaches for tracking unreclaimed memory

Robert Raschke rtrlists at googlemail.com
Wed Oct 28 15:59:36 GMT 2009

On Wed, Oct 28, 2009 at 3:48 PM, Garrett Smith <g at rre.tt> wrote:

> Yup, I'm familiar with those flags (and actually have read the spec, a
> few times even :)
> I need both non-exclusive/non-auto-delete so that the queue is
> preserved when either the creating connection or the last consumer
> goes away. Various agents come and go (restarting is one example, but
> there are other cases). Not to preach to the choir, but one of the
> benefits of async messaging is you can insulate from dropped
> connections.
> It sounds like I'm left with the option of running a cleanup/check
> process occasionally to ensure that we don't run into queues piling
> up. No other options, given exclusive=false and autodelete=false?
> I know that the expires/TTL is ignored in rabbit, and is perhaps not
> entirely fleshed out in the 0.8 spec, but it seems an important
> feature wrt resource resource management.
Unless you've also got persitant messages, why not have auto-delete queues
that every producer and consumer just declares up front? If no-one's around
using that queue, it goes away, once someone needs it, the declare makes it

Or am I missing something?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091028/db6ae3fb/attachment.htm 

More information about the rabbitmq-discuss mailing list