Reviewed: https://review.openstack.org/341806
Committed:
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=56b8a621509af9688e6fcaa98e511702d68ba0b2
Submitter: Jenkins
Branch: master
commit 56b8a621509af9688e6fcaa98e511702d68ba0b2
Author: Dustin Lundquist <dus...@null-ptr.net>
Date: Wed Jul 13 13:54:44 2016 -0700
haproxy ns driver: set global haproxy maxconn
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.
Change-Id: I950abaed780d7df33f0ab5c682bf583aa581889f
Closes-Bug: 1544861
** 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/1544861
Title:
LBaaS: connection limit does not work with HA Proxy
Status in neutron:
Fix Released
Bug description:
connection limit does not work with HA Proxy.
It sets at frontend section like:
frontend 75a12b66-9d2a-4a68-962e-ec9db8c3e2fb
option httplog
capture cookie JSESSIONID len 56
bind 192.168.10.20:80
mode http
default_backend fb8ba6e3-71a4-47dd-8a83-2978bafea6e7
maxconn 50000
option forwardfor
But above configuration does not work.
It should be set at global section like:
global
daemon
user nobody
group haproxy
log /dev/log local0
log /dev/log local1 notice
stats socket
/var/lib/neutron/lbaas/fb8ba6e3-71a4-47dd-8a83-2978bafea6e7/sock mode 0666
level user
maxconn 50000
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1544861/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
