Red Hat Bugzilla – Bug 971571
cinder appears to be leaking qpid exchanges
Last modified: 2016-04-26 18:54:34 EDT
+++ This bug was initially created as a clone of Bug #960539 +++
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.
* Start OpenStack
* After a while, run qpid-stat -e lists open exchanges.
Actual results: Many exchanges reported.
Expected results: Few/no exchanges reported
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: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.
--- Additional comment from David Ripton on 2013-06-06 16:12:52 EDT ---
Related upstream bugs:
Worked around via setting in cinder-dist.conf.
verified using openstack-cinder-2013.1.2-3.el6ost.noarch
Edited Doc Text
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.