[Bug 1515278] Re: rabbit queues should expire when unused
Ubuntu Foundations Team Bug Bot
1515278 at bugs.launchpad.net
Thu Feb 11 20:26:59 UTC 2016
The attachment "Trusty-Kilo Patch" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1515278
Title:
rabbit queues should expire when unused
Status in oslo.messaging:
Fix Released
Status in oslo.messaging package in Ubuntu:
Fix Committed
Status in oslo.messaging source package in Trusty:
In Progress
Status in oslo.messaging source package in Wily:
In Progress
Bug description:
RabbitMQ supports queue-level TTLs as described here:
https://www.rabbitmq.com/ttl.html#queue-ttl
This should be used when declaring queues in order to clean up queues
that are orphaned for various reasons.
This is an important complement to auto_delete queues. Queues marked
auto_delete are only deleted if a consumer existed at some point, and
then disconnected, resulting in zero consumers.
Consider the following scenario: a client declares a queue
(auto_delete) and binds it to a fanout exchange, but before the client
can consume from the queue, it dies.
Because there was never (and will never be) a consumer of this queue,
the auto_delete logic does not fire. The queue will live forever, and
will collect a copy of every message that is sent to the bound fanout
exchange. Given enough published messages to the exchange, the queue
will eventually consume all available memory on the broker.
This is bad and we should avoid it by setting a reasonable TTL.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1515278/+subscriptions
More information about the Ubuntu-sponsors
mailing list