[Bug 1515278] Re: rabbit queues should expire when unused

[Corey Bryant]

Jorge,

I've uploaded this to wily and it will require SRU team review before it
gets into wily-proposed.  Can you update the bug description with the
standard SRU sections?  [Impact], [Test Case], and [Regression
Potential].

Thanks,
Corey

** Summary changed:

- rabbit queues should expire when unused
+ [SRU] rabbit queues should expire when unused

-- 
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:
  [SRU] 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