Well, not at all :-) So, minconn is an upper limit for incoming connections , is right ?
And maxconn will be the new upper limit for incoming connections when the number of connection ( concurrent ? ) on the backend is equal to fullconn. is right ? And what does it happen if "the number on the backend" < fullconn and incoming connections > minconn ? are the new one queued ? Thanks and regards 2013/4/24 Baptiste <[email protected]> > Hi, > > Long time nobody asked for fullconn information :) > > fullconn allows HAProxy to manage connections on your server. > It means that HAProxy will increase connection opened on the server, > from minconn to maxconn. And maxconn will be reached when the number > of connection on the backend is equal to fullconn. > > I hope this is a bit more clearer. > > Baptiste > > > On Tue, Apr 23, 2013 at 11:22 AM, Jose María Zaragoza > <[email protected]> wrote: > > > > Hello: > > > > > > I'm reading about fullconn parameter in > > > > https://code.google.com/p/haproxy-docs/wiki/fullconn > > > > and I don't get the example > > > > > > # The servers will accept between 100 and 1000 concurrent connections > each > > # and the maximum of 1000 will be reached when the backend reaches 10000 > > # connections. > > backend dynamic > > fullconn 10000 > > server srv1 dyn1:80 minconn 100 maxconn 1000 > > server srv2 dyn2:80 minconn 100 maxconn 1000 > > > > > > I don't understand what minconn is for . Is it a lower limit for > concurrent > > connections? > > "The server will accept between 100 and 1000 concurrent connections" > > And if is there 50 concurrent connections to backend ? > > > > If the server accepts up to 1000 concurrent connections, I guess 1000 is > > always the upper limit > > So, what fullconn is for ? is for concurrent connections to backend ? > > > > I don't understand this limits > > > > Thanks and regards > > > > > > > > >
