Along this same vein... We're using HAProxy to execute seamless mid-day deployments of high-volume critical services. The http-server-close option is set. The backend of an example service is like so:
server svr2 192.168.1.19:80 check server svr2_staging 192.168.1.19:8080 disabled check Our deployment system is configured to copy new binaries to the svr2_staging server, then use the stats socket to change the svr2_staging state to "ready" and the svr2 state to "drain". My question is how can I be sure all existing sessions to the svr2 server are closed before I start copying binaries to it? On Wed, Oct 29, 2014 at 12:06 PM, Baptiste <[email protected]> wrote: > On Fri, Oct 24, 2014 at 4:37 PM, Ian Cooke <[email protected]> wrote: > > Hi, > > > > Can haproxy change the backend for an existing session? I have a > stateless > > client/server and I thought 'redispatch' did what I want but it seems > that's > > only for the initial connection. What I'd like is for a client that's > > already been connected to maintain the frontend's connection but change > the > > session's backend server if the one it's connected to goes down. > > > > Thanks, > > Ian > > Hi, > > maybe http-server-close is the option you're looking for. > > Baptiste > > --
