neutron/releasenotes/notes/keepalived-state-change-server-threads-9ed775e7533dd1a0.yaml
venkata anil 70ea188f5d New option for num_threads for state change server
Currently max number of client connections(i.e greenlets spawned at
a time) opened at any time by the WSGI server is set to 100 with
wsgi_default_pool_size[1].

This configuration may be fine for neutron api server. But with
wsgi_default_pool_size(=100) requests, state change server
is creating heavy cpu load on agent.
So this server(which run on agents) need lesser value i.e
can be configured to half the number of cpu on agent

We use "ha_keepalived_state_change_server_threads" config option
to configure number of threads in state change server instead of
wsgi_default_pool_size.

[1] https://review.openstack.org/#/c/278007/

DocImpact: Add new config option -
ha_keepalived_state_change_server_threads, to configure number
of threads in state change server.

Closes-Bug: #1581580
Change-Id: I822ea3844792a7731fd24419b7e90e5aef141993
2016-09-23 17:07:12 +00:00

11 lines
521 B
YAML

---
upgrade:
- 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.