On Mon, Aug 11, 2014 at 1:34 PM, Lukas Tribus <[email protected]> wrote: > I would say this simple depends on the http mode you use. > > When you use tunnel mode (default in pre-1.5 releases), it obviously > sticks to the same backend server. When you use close mode, both > server and client connections are closed after the response (no > keepalive). > > Instead, for your environment you should use http-server-close: > http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20http-server-close
Does this actually close the HTTP session, close the sockets, etc? Because of the large number of requests per second (~150k over our whole cluster) I'm afraid that the overhead of connection establishment might be problematic for us if so. > This way, frontend keeps doing keepalive with your clients, maintaining > long-lived sessions, while your backend closes the connection after > the response, thus, leastconn works for every single requests. Is there a hybrid mode, where connections (in the TCP sense) are kept alive between HAProxy and the backends, but where individual HTTP requests are potentially balanced to any of the existing backend connections? You mentioned pre-1.5 (we're on 1.4.x), has something changed in 1.5 that might be a fit for our use case? Thanks, - Dan
