Bug 1310807

Summary: Utilize QoS to prevent excessive client side queueing of messages
Product: Red Hat OpenStack Reporter: John Eckersberg <jeckersb>
Component: python-oslo-messagingAssignee: John Eckersberg <jeckersb>
Status: CLOSED ERRATA QA Contact: Udi Shkalim <ushkalim>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: apevec, dmaley, fpercoco, ggillies, jeckersb, jschluet, lhh, mfuruta, mwagner, plemenko, yeylon
Target Milestone: ga   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-oslo-messaging-2.5.0-4.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1295896 Environment:
Last Closed: 2016-04-07 21:30:03 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:
Bug Depends On: 1295896    
Bug Blocks: 1302861, 1302873    

Comment 3 Udi Shkalim 2016-03-09 10:14:38 UTC 
Verified on:python-oslo-messaging-2.5.0-4.el7ost.noarch

Added rabbit_qos_prefetch_count=50 in nova.conf and neutron.conf under the rabbit section and restart the services.

[root@overcloud-controller-2 ~]# rabbitmqctl list_channels name prefetch_count  | grep 50
10.35.169.13:48413 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48472 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48475 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48478 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48479 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48482 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48484 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48491 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48669 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48737 -> 10.35.169.13:5672 (1)	50
10.35.169.13:48836 -> 10.35.169.13:5672 (1)	50
10.35.169.13:54470 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54472 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54474 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54476 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54479 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54482 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54483 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54486 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54659 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54665 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54669 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54672 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54675 -> 10.35.169.15:5672 (1)	50
10.35.169.13:54747 -> 10.35.169.15:5672 (1)	50
10.35.169.13:56116 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56170 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56171 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56173 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56174 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56176 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56185 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56187 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56188 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56192 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56359 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56370 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56384 -> 10.35.169.14:5672 (1)	50
10.35.169.13:56528 -> 10.35.169.14:5672 (1)	50
Comment 4 errata-xmlrpc 2016-04-07 21:30:03 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.

https://rhn.redhat.com/errata/RHEA-2016-0603.html