Back to bug 1381619
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| anil venkata | 2016-10-04 14:59:31 UTC | Blocks | 1381620 | |
| anil venkata | 2016-10-04 15:02:26 UTC | Target Release | 7.0 (Kilo) | 9.0 (Mitaka) |
| Assaf Muller | 2016-10-04 16:31:46 UTC | Status | NEW | ASSIGNED |
| Assignee | amuller | vkommadi | ||
| Assaf Muller | 2017-05-08 18:02:13 UTC | Keywords | Triaged | |
| anil venkata | 2017-06-13 09:48:21 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | openstack-neutron-8.3.0-3.el7ost | |||
| anil venkata | 2017-06-13 09:50:21 UTC | Doc Text | Prior to this update, with 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. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2017-06-28 14:16:38 UTC | Status | MODIFIED | ON_QA |
| Ofer Blaut | 2017-07-03 13:34:23 UTC | CC | oblaut | |
| QA Contact | tfreger | ekuris | ||
| Eran Kuris | 2017-07-04 08:52:51 UTC | Status | ON_QA | VERIFIED |
| Scott Lewis | 2017-07-11 10:16:42 UTC | Target Milestone | async | zstream |
| Martin Lopes | 2017-07-12 01:34:01 UTC | CC | mlopes | |
| Doc Text | Prior to this update, with 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. | 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. |
||
| errata-xmlrpc | 2017-07-12 03:36:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-07-12 13:18:57 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-07-12 09:18:57 UTC |
Back to bug 1381619