openstack/neutron
Code Issues Proposed changes

Set haproxy nbthread[1] to 2

Browse Source 
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>
This commit is contained in:
Miro Tomaska
2025-07-25 15:18:17 -04:00
parent f9067a7190
commit 0a044ce384
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
neutron/common/metadata.py
View File

@@ -45,6 +45,7 @@ global
user %(user)s user %(user)s
group %(group)s group %(group)s
maxconn 1024 maxconn 1024
nbthread 2
pidfile %(pidfile)s pidfile %(pidfile)s
daemon daemon

8
releasenotes/notes/haproxy-nbthread-a658040c98639b47.yaml Normal file
View File

@@ -0,0 +1,8 @@
---
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>`_.