Number of Rabbitmq queues is growing from failover to failover
Bug #1414674 reported by
Alexey Khivin
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Unassigned | ||
Juno |
Fix Released
|
High
|
Pavlo Shchelokovskyy | ||
oslo.messaging |
Fix Released
|
High
|
Unassigned |
Bug Description
When using oslo.messaging with RabbitMQ driver
On every start Heat creates 4 queues with the names like
b21828bd-
b21828bd-
engine
engine.node-4
two of them have contant names and other two have random names.
So, the number of randomly named queues increases every time the Heat restarts
These queues have no "auto_delete" and "x-expire" options, so they will not be deleted until RabbitMQ cluster restarted
description: | updated |
Changed in oslo.messaging: | |
assignee: | nobody → sajuptpm (sajuptpm) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in oslo.messaging: | |
importance: | Undecided → High |
Changed in heat: | |
status: | Triaged → Fix Committed |
Changed in oslo.messaging: | |
status: | New → Invalid |
tags: | added: juno-backport-potential |
Changed in heat: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-3 → 2015.1.0 |
Changed in oslo.messaging: | |
assignee: | Mehdi Abaakouk (sileht) → nobody |
tags: | removed: juno-backport-potential |
Changed in oslo.messaging: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is this the same as https:/ /bugs.launchpad .net/oslo. messaging/ +bug/1406629 ?