Hi, On 23.10.2012 13:55, Finn Arne Gangstad wrote: > Hi, > > We're running haproxy in front of many services that are written in > Java. From time to time, the Java applications need to pause for a > while and do garbage collection. It would be extremely beneficial if > haproxy could be configured to redispatch all requests that are > currently in limbo on a GCing server to some other server. > > haproxy.cfg typically looks like this: > > frontend > timeout http-request 30s > maxconn 100000 > ... > > backend > balance roundrobin > server s1 ... maxconn 10 > server s2 ... maxconn 10 > server s3 ... maxconn 10 > .. > > Each request is a reasonably simple GET request that typically takes > 10-20ms to process. This works great until a server needs to GC, then > the query will hang for a few seconds. Iam not quit sure, but I think you can play with timeout server and option redispatch and retries, so that when GC occours the request would be redispatched to the next server in the backend.
> Tanks > Finn Arne > > thomas
