Hello Neil, On Sat, Feb 19, 2011 at 11:38:10PM +0000, Neil Prockter wrote: > Hello > > I think I've got to the bottom of this, thanks to the straces and some > lucky guesswork. > > the trouble occurs when the backend server does not have a entry in the > DNS reverse lookup zone. > > I've now got a cluster of identical backends the ones that have reverse > lookup entries come back straight away the ones without take over 5 seconds.
OK so now that makes a lot of sense. > The main thing that tipped me off was running haproxy and tomcat on the > same server (which did not have a reverse lookup entry) the problem > could be solved by adding a etc hosts entry for the form of the name > used in the server config line. > > I guess I'll add entries for all my servers but perhaps a fix in haproxy > is also warranted? What fix do you mean ? Haproxy can't force your servers to disable DNS resolving. Regards, Willy
