fd30dfb867
Following ideas here: https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit Make sure old messages with no consumer are dropped after the message TTL of 10 mins, longer than the 1 min RPC timeout. Also ensure queues expire after an hour of inactivity, so queues from removed nodes or renamed nodes don't grow over time. Change-Id: Ifb28ac68b6328adb604a7474d01e5f7a47b2e788
13 lines
643 B
YAML
13 lines
643 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
In RabbitMQ, messages now have a TTL of 10 minutes and inactive queues will
|
|
expire after 1 hour. These queue arguments can be changed dynamically at
|
|
runtime [1], but it should be noted that applying a TTL to queues which
|
|
already have messages will discard the messages when specific events occur.
|
|
See [2] for more details. Note that the contents of the RabbitMQ
|
|
definitions.json are now changed, meaning RabbitMQ containers will be
|
|
restarted on next deploy/upgrade.
|
|
[1] https://www.rabbitmq.com/queues.html#optional-arguments
|
|
[2] https://www.rabbitmq.com/ttl.html#per-message-ttl-caveats
|