Hey Baptiste, Thanks for the reply.
I already have maxconn set up on my config. I can see that the number of connections coming through are more than the maxconn value. I am running on nbproc > 1, So I have divided the maxconn / nbproc So if my server can only handle 4000 / sec, I have set the maxconn to 4000 / nbproc On Wed, Apr 27, 2016 at 8:28 PM, Baptiste <bed...@gmail.com> wrote: > Hi Vipin > > > I have haproxy set up in production, operating in keepalive in mode http. > > ok > > > In keepalive a single session can send multiple connections. > > you don't send a connection, you open it or you send a request. Could > you please clarify this point? > > > Is there a way to reject connections? > > Yes > > > Upon reaching total number of conenctions in backend? > > Yes > > > I tried using an acl on be_conn. > > This count does not reflect the total http requests that > > are coming through to the backend. > > Well, the documentation says it clearly: "the number of currently > established connections on the backend," > > I think I start to understand. You may want to try "maxconn" on the server > line. > It will prevent too many queries from hitting your servers and protect > them again spikes. > > > I do want to use keepalive and not move to http-close or forceclose. > > Server's maxconn is compatible with keep-alive mode. > > Baptiste >
