From: Olivier Houchard <ohouchard@haproxy.com>
Date: Thu, 6 Aug 2026 12:39:39 +0000 (+0200)
Subject: DOC: Document limitations of tune.fd.tables
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=36ab78f7b4f4a8113e38d35cae2ce8f6c381116a;p=thirdparty%2Fhaproxy.git

DOC: Document limitations of tune.fd.tables

Document that when multi-queue is used with tune.fd.tables set to
per-thread-group, then connections will only be load-balanced across
threads from the same thread group.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 0656a7783..7498f3182 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -4788,6 +4788,9 @@ tune.listener.multi-queue { on | fair | off }
   using "off" for troubleshooting, or for situations where connections are
   short-lived and it is estimated that the operating system already provides a
   good enough distribution. The default is "on".
+  Please not that when tune.fd.tables is set to "per-thread-group",
+  connections will only be load-balanced across threads of a same thread
+  group.
 
 tune.lua.bool-sample-conversion { normal | pre-3.1-bug }
   Explicitly tell haproxy how haproxy sample objects should be handled when