[rabbitmq-discuss] per-queue message TTLs [was Re: Bound Queues]

Wed Apr 14 19:48:24 BST 2010

On Wed, Apr 14, 2010 at 11:13 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Dan Di Spaltro wrote:
> > On Wed, Apr 14, 2010 at 4:13 AM, Tony Garnock-Jones <tonyg at lshift.net>
> wrote:
> >> if only it were a per *queue* ttl, it'd be so much easier!
> > ttl's on a queue level would be very useful to us
>
> That's a really interesting idea, and it is a lot easier to implement
> than per-message TTLs.
>
> So here is a question to all RabbitMQ users who have been asking /
> secretly wishing for TTLs: Would per-queue TTLs, i.e. all messages
> getting the same TTL when they are enqueued, be good enough (or even
> preferable) for you? Or do you definitely need to be able to specify
> TTLs on per-message basis (and if so, what is the use case)?
>

Per-queue would be far more useful IMO.   Display the TTL's in rabbitmqctl
list_queues and in the rabbitmq-status plugin and it'll be really easy to
allow users to figure out why their messages are disappearing after $TTL
seconds.   It also makes the life of the administrator easier, since it
would be visible without peeking at messages.

-Al

Regards,
>
> Matthias.
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100414/887b5a3d/attachment.htm 