Bug 1381619

Summary: UnixDomainWSGIServer keepalived state change listener in L3 agent has an uncapped number of threads, overloading node
Product: Red Hat OpenStack Reporter: anil venkata <vkommadi>
Component: openstack-neutronAssignee: anil venkata <vkommadi>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: urgent Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: amuller, bperkins, bschmaus, chris.fields, chrisw, dchia, dhill, jraju, mflusche, mlopes, nyechiel, oblaut, srevivo, tfreger
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-8.3.0-3.el7ost Doc Type: Bug Fix
Doc Text:
Prior to this update, when using wsgi_default_pool_size(=100) concurrent requests, the state change server would create a heavy CPU load on the l3 agent. With this update, a new option `ha_keepalived_state_change_server_threads` has been added to configure the number of concurrent threads spawned for keepalived server connection requests; higher values increase the CPU load on the agent nodes. The default value is half of the number of CPUs present on the node. This allows operators to tune the number of threads to suit their environment. With more threads, simultaneous requests for multiple HA routers state change can be handled faster. As a result, ha_keepalived_state_change_server_threads can be configured to avoid high load on l3 agents.
Story Points: ---
Clone Of: 1381618
: 1381620 (view as bug list) Environment:
Last Closed: 2017-07-12 13:18:57 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: 1315114, 1381618    
Bug Blocks: 1381620    

Comment 2 Eran Kuris 2017-07-04 08:52:51 UTC
$ rpm -qa |grep openstack-neutron-8.3
openstack-neutron-8.3.0-11.el7ost.noarch
$ cat /etc/yum.repos.d/latest-installed 
9   -p 2017-06-29.1
fixed verified

Comment 5 errata-xmlrpc 2017-07-12 13:18:57 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://access.redhat.com/errata/RHBA-2017:1736