Hi Kevin, On Thu, May 24, 2012 at 09:01:43PM -0500, Lange, Kevin M. (GSFC-423.0)[RAYTHEON COMPANY] wrote: > Monsieur Tarreau, > > Actually, we are seeing frontend service availability flapping. This morning > particularly. Missing from my snippet is the logic for an unplanned outage > landing page, that our customers were seeing this morning, so it haproxy > truly is "timing out" and marking each backend as down until there are no > backend servers available, throwing up the unplanned outage landing page.
I'm not surprized, if you observe that checks should last more than 1 second to work correctly :-/ I have tested your configuration here. First I can say it's not bad reporting, as the timers in the logs are the correct ones. Second, I noticed a bug, when both "timeout check" and "timeout connect" are set, haproxy uses the largest of the two for the check ! The reason is that it did not displace the task in the queue upon connection establishment if the check timeout is smaller than the connect timeout. I've fixed it now. This aside, I could not reproduce the issue here. I agree with Baptiste, a tcpdump would certainly help. Maybe we're facing corner case issues which I did not test, such as servers sending partial responses or things like this, I don't know. Regards, Willy
