Reviewed: https://review.opendev.org/c/openstack/neutron/+/955951 Committed: https://opendev.org/openstack/neutron/commit/0a044ce38407d9ac196bc3fabdc16acf8fbb29fa Submitter: "Zuul (22348)" Branch: master
commit 0a044ce38407d9ac196bc3fabdc16acf8fbb29fa Author: Miro Tomaska <[email protected]> Date: Fri Jul 25 15:18:17 2025 -0400 Set haproxy nbthread[1] to 2 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 <[email protected]> ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2120668 Title: Limit threads for metadata haproxy Status in neutron: Fix Released Bug description: On very large enviroments with many agents, the spawned haproxy process can cause "too many open files" exceptions when haproxy is not bound by any other restrictions e.g. CPU affinity. Since the haproxy is not resource intensive process, we can limit haproxy to 2 threads. This can be achieved with `nbthread` config[1] [1] www.haproxy.com/documentation/haproxy-configuration- manual/latest/#nbthread To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2120668/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
