Haproxy uses two separate maxconn values: the maxconn setting in the
global context is used to adjust file descriptor limits and allocate
resources, while the maxconn setting in the frontend context controls if
additional connections are accepted on that frontend.
This patch adds a maxconn to the global context equal to the sum of the
connection limit on each listener. For listeners which no connection
limit specified, we don't set this value and leave it at haproxy's
default (2000).
Reviewed: https:/ /review. openstack. org/369089 /git.openstack. org/cgit/ openstack/ octavia/ commit/ ?id=f37b3e5422a ecd9dc341929112 62d0fa03800fb2
Committed: https:/
Submitter: Jenkins
Branch: master
commit f37b3e5422aecd9 dc34192911262d0 fa03800fb2
Author: Stephen Balukoff <email address hidden>
Date: Mon Sep 12 17:16:30 2016 -0700
Set haproxy global connection limit
Haproxy uses two separate maxconn values: the maxconn setting in the
global context is used to adjust file descriptor limits and allocate
resources, while the maxconn setting in the frontend context controls if
additional connections are accepted on that frontend.
This patch adds a maxconn to the global context equal to the sum of the
connection limit on each listener. For listeners which no connection
limit specified, we don't set this value and leave it at haproxy's
default (2000).
Change-Id: I30f3cf5f469db9 53a0002721a315f 02694621b7d
Partial-Bug: #1544861