Perhaps, but we are running nginx on the same physical boxes as the webservers, not in front of haproxy, so it is not in a position where it can retry the request on a different server. Retrying the request on the same server won't help with most classes of problems.
client->open internet->haproxy->internal network->nginx->webserver On Wed, Aug 25, 2010 at 12:16 PM, Willy Tarreau <[email protected]> wrote: > On Wed, Aug 25, 2010 at 12:06:32PM -0700, Dustin Moskovitz wrote: > > Thanks for all the input guys. Sounds like haproxy is the wrong place to > > solve the problem, so we've instead decided to remove nginx from the > > equation (which was only providing gzip capabilities that we can > implement > > directly in our webserver). Thus, requests failing on the webserver will > > actually result in disconnects, which will allow haproxy to redispatch > the > > request to a new server. > > Well, I may be wrong, but I *think* that when nginx acts as a caching > proxy, it is able to retry. You might want to check this and perhaps > reintroduce it. Haproxy+Nginx are generally known to form a complete > and reliable solution together. > > Regards, > Willy > >
