yahoo-eng-team team mailing list archive

[Dustin Lundquist <dustin@xxxxxxxxxxxx>]

Resurrecting this bug, since we ran into it. It looks like maxconn in
HAproxy is a bit more nuanced: the global maxconn setting will cause
HAProxy is used to compute the maximum number of socket and file
descriptor ulimits, while the listener maxconn is used to limit
connections on a specific listener. The global maxconn setting should
equal or greater than the sum of the maxconn for each listener. This can
be verified by observing the file descriptor limits in /proc/$PID/limits
once HAproxy has started.

** Changed in: neutron
       Status: Expired => Confirmed

-- 
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:
  Confirmed

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