From RDO forum user bostrick: http://openstack.redhat.com/forum/discussion/85/is-nova-conductor-leaking-qpid-exchanges Description of problem: After several hours of operation, there are a large number of qpid exchanges in existence, with a new one being created every ~10s. To reproduce: * Start OpenStack * After a while, run qpid-stat -e lists open exchanges. Actual results: Many exchanges reported. Expected results: Few/no exchanges reported Additional info: qpid-printevents is displaying transactions similar to the following every 10 secs: org.apache.qpid.broker:exchangeDeclare ... exName=d75b1d8f76ea46eead02b7480dd28cdf ... org.apache.qpid.broker:queueDeclare ... qName=d75b1d8f76ea46eead02b7480dd28cdf ... org.apache.qpid.broker:bind ... exName=d75b1d8f76ea46eead02b7480dd28cdf ... org.apache.qpid.broker:subscribe ... qName=d75b1d8f76ea46eead02b7480dd28cdf ... org.apache.qpid.broker:unsubscribe ... org.apache.qpid.broker:queueDelete ... qName=d75b1d8f76ea46eead02b7480dd28cdf notably missing is a complement to "exchangeDeclare" to clean it up. tracing qpid client ports, nova-conductor seems to be the culprit.
Related upstream bugs: https://bugs.launchpad.net/oslo/+bug/1033915 https://bugs.launchpad.net/nova/+bug/1178375
The issue is in the code copied from oslo-incubator (ex openstack-common): $PROJECT/openstack/common/rpc/impl_qpid.py
Workaround from upstream bug https://bugs.launchpad.net/oslo/+bug/1178375/comments/7
This was fixed by a workaround in RDO Grizzly openstack-nova-2013.1.2-3: http://pkgs.fedoraproject.org/cgit/openstack-nova.git/diff/0002-avoid-code-path-causing-qpid-exchange-leaks.patch?h=el6-grizzly&id=f858dc5c60b9c7aac1c26011fbdec164bdeecc82 Alternative (backward-incompatible for in-place upgrade) fix was proposed for stable/grizzly https://review.openstack.org/44893