0a044ce384
The haproxy that gets spawned by agents can cause `too many open files` exceptions on very large deployments. Since haproxy is not resource intensive process, we can limit it to only use 2 threads to mitigate this issue. [1] www.haproxy.com/documentation/haproxy-configuration-manual/latest/#nbthread Closes-bug: #2120668 Change-Id: I70b2461d65f3e9967bea1239eac3c1ccb52b3138 Signed-off-by: Miro Tomaska <mtomaska@redhat.com>
8 lines
350 B
YAML
8 lines
350 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Limit the number of threads used by the metadata haproxy service to 2 using
|
|
the nbthread configuration. This prevents haproxy from spreading across many
|
|
threads when the process lacks other restrictions like CPU affinity.
|
|
For more information, see bug
|
|
`2120668 <https://bugs.launchpad.net/neutron/+bug/2120668>`_. |