One other thought I had which is probably more complicated is timeouts based on ACLs. Specifically so I can set the timeout on specific URLs to be longer than the default.
I think both features would be useful but either of them might be good enough to get around the issues I'm having. -Joe On Oct 4, 2010, at 3:46 PM, Joe Williams wrote: > > Is it possible for haproxy to basically kill (and/or retry) established > backend connections for a failed backend server as soon as it fails a content > check? Basically I have some long running requests that are expected to hang, > in some cases the server they are connected to goes unavailable, failing the > health check, but the connection sits until the timeout is reached while no > new connections are routed to it. Ideally I would be able to keep my high > server timeout but have those connections closed and retried (similar to > redispatch/retry) if there was a health check failure after they were > established. From what I can tell redispatch and retries don't cover this > case. Thoughts? > > Thanks. > > -Joe > > > > Name: Joseph A. Williams > Email: [email protected] > Blog: http://www.joeandmotorboat.com/ > Twitter: http://twitter.com/williamsjoe > > Name: Joseph A. Williams Email: [email protected] Blog: http://www.joeandmotorboat.com/ Twitter: http://twitter.com/williamsjoe
