Patrick Hemmer <haproxy@...> writes: > From: Willy Tarreau <w <at> 1wt.eu> > > Sent: 2014-01-25 05:45:11 E > > Till now that's exactly what's currently done. The servers are marked > "almost dead", so the first check gives the verdict. Initially we had > all checks started immediately. But it caused a lot of issues at several > places where there were a high number of backends or servers mapped to > the same hardware, because the rush of connection really caused the > servers to be flagged as down. So we started to spread the checks over > the longest check period in a farm. > > Is there a way to enable this behavior? In my > environment/configuration, it causes absolutely no issue that all > the checks be fired off at the same time. > As it is right now, when haproxy starts up, it takes it quite a > while to discover which servers are down. > -Patrick >
I faced the same problem in http://thread.gmane.org/ gmane.comp.web.haproxy/14644 After much contemplation, I decided to just patch away the initial spread check behavior: https://github.com/sayap/sayap-overlay/blob/master/net- proxy/haproxy/files/haproxy-immediate-first-check.diff
