Re: change backend for an existing connection?

Hi Thomas, thanks for the suggestion! I'm hoping for a built-in solution with the existing stats data. Would scur=0 on the server stats be an accurate test? I'm dubious because I tested disabling http-server-close and the active server in question still shows scur of 0 most of the time; the request

Re: change backend for an existing connection?

Hi, On 29.10.2014 23:09, Tom Keyser wrote: > 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: > > serversvr2 192.168.1.19:80

Re: change backend for an existing connection?

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

Re: change backend for an existing connection?

On Fri, Oct 24, 2014 at 4:37 PM, Ian Cooke 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

change backend for an existing connection?

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 chang