Orphan exchanges in Qpid and lack of option for making queues [un]durable
Bug #1178375 reported by
Salman Baset
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Russell Bryant | ||
Cinder |
Fix Released
|
Undecided
|
Russell Bryant | ||
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Russell Bryant | ||
OpenStack Heat |
Fix Released
|
Undecided
|
Russell Bryant | ||
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned | ||
Havana |
Fix Released
|
Medium
|
Alan Pevec | ||
neutron |
Fix Released
|
Medium
|
Russell Bryant | ||
oslo-incubator |
Fix Released
|
Medium
|
Russell Bryant | ||
oslo.messaging |
Fix Released
|
Medium
|
Ken Giusti |
Bug Description
Start qpid, nova-api, nova-scheduler, and nova-conductor, and nova-compute.
There are orphan direct exchanges in qpid. Checked using qpid-config exchanges. The exchanges continue to grow, presumably, whenever nova-compute does a periodic update over AMQP.
Moreover, the direct and topic exchanges are by default durable which is a problem. We want the ability to turn on/off the durable option just like Rabbit options.
affects: | oslo → nova |
affects: | nova → oslo |
Changed in oslo: | |
assignee: | William Henry (whenry) → Russell Bryant (russellb) |
Changed in heat: | |
milestone: | none → havana-3 |
Changed in ceilometer: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | none → havana-3 |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in oslo: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in oslo: | |
milestone: | havana-3 → 2013.2 |
Changed in ceilometer: | |
milestone: | havana-3 → 2013.2 |
Changed in heat: | |
milestone: | havana-3 → 2013.2 |
Changed in cinder: | |
milestone: | havana-3 → 2013.2 |
Changed in neutron: | |
milestone: | havana-3 → 2013.2 |
Changed in nova: | |
milestone: | havana-3 → 2013.2 |
Changed in oslo.messaging: | |
status: | New → Confirmed |
Changed in oslo: | |
importance: | Undecided → Medium |
Changed in oslo.messaging: | |
importance: | Undecided → Medium |
Changed in oslo.messaging: | |
milestone: | none → icehouse-1 |
Changed in oslo.messaging: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
status: | New → Invalid |
tags: | removed: grizzly-backport-potential |
no longer affects: | nova/grizzly |
Changed in oslo.messaging: | |
milestone: | icehouse-1 → 1.3.0 |
To post a comment you must log in.
I've been seeing this a lot lately using QPID. I think they are RPC reply queues from conductor but I'm not sure. Fortunately on most systems, QPID doesn't support durable queues since it requires extra packages. Restarting QPID will clear the orphaned queues out.
Also, I think there is a Redhat bug related to this in case anyone is interested.
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=960539