From cefbbd98116cc97b43711b784638789c5557e7e6 Mon Sep 17 00:00:00 2001 From: Tim Duesterhus Date: Wed, 27 Nov 2019 22:35:27 +0100 Subject: [PATCH] DOC: Clarify behavior of server maxconn in HTTP mode In HTTP mode the number of concurrent requests is limited, not the number of actual connections. --- doc/configuration.txt | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 2fadc4336..1e15ba4ec 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -11646,13 +11646,19 @@ downinter maxconn The "maxconn" parameter specifies the maximal number of concurrent connections that will be sent to this server. If the number of incoming - concurrent requests goes higher than this value, they will be queued, waiting - for a connection to be released. This parameter is very important as it can + concurrent connections goes higher than this value, they will be queued, + waiting for a slot to be released. This parameter is very important as it can save fragile servers from going down under extreme loads. If a "minconn" parameter is specified, the limit becomes dynamic. The default value is "0" which means unlimited. See also the "minconn" and "maxqueue" parameters, and the backend's "fullconn" keyword. + In HTTP mode this parameter limits the number of concurrent requests instead + of the number of connections. Multiple requests might be multiplexed over a + single TCP connection to the server. As an example if you specify a maxconn + of 50 you might see between 1 and 50 actual server connections, but no more + than 50 concurrent requests. + maxqueue The "maxqueue" parameter specifies the maximal number of connections which will wait in the queue for this server. If this limit is reached, next