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 0656a778394e72552ac7f7a4e3de2cca95cdb517..7498f3182b6243abad17d19da2a4bb87b60cfdb8 100644 (file)
--- 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