Bug 971565

Summary: nova-compute appears to be leaking qpid exchanges
Product: Red Hat OpenStack Reporter: Flavio Percoco <fpercoco>
Component: openstack-novaAssignee: Nikola Dipanov <ndipanov>
Status: CLOSED ERRATA QA Contact: Jaroslav Henner <jhenner>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: dallan, dneary, eglynn, jhenner, jturner, ndipanov, sgordon, ykaul
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2013.1.2-2.el6ost Doc Type: Bug Fix
Doc Text:
The Compute Conductor (openstack-nova-conductor) service was not correctly closing Qpid message exchanges. As a result after several hours of operations many open exchanges would remain in existence. The Compute Conductor service has been updated and now closes Qpid message exchanges correctly when they are no longer needed.
Story Points: ---
Clone Of: 960539 Environment:
Last Closed: 2013-06-27 17:16:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Flavio Percoco 2013-06-06 20:12:58 UTC
+++ 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.

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.

Comment 4 Jaroslav Henner 2013-06-13 14:16:04 UTC
# qpid-stat -e | wc -l
28
# qpid-config exchanges | wc -l
27

Whereas on unfixed system

# qpid-config exchanges | wc -l
557
# qpid-stat -e | wc -l
577

Comment 7 errata-xmlrpc 2013-06-27 17:16:29 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-0968.html