Hi Willy Thanks, I'll send future traces to you directly. I understand the hatred of bulky email files!
So I think I found the problem but would love your take on it. Our web applications and services in our haproxy backend are using keepalive in their connection headers. I understand in haproxy v1.4 keepalives are ok from the client side but not from the server side, correct? So I added the option to http-server-close on our haproxy web service server and it appears to have stopped this random half loaded data stream issue. Can you explain how having keepalive coming from the server side application connection headers could cause this issue? Could you give a brief description of what happens when haproxy receives a keepalive header but does not have http-server-close option set? Thanks as always for your help! -----Original Message----- From: Willy Tarreau [mailto:[email protected]] Sent: Wednesday, May 28, 2014 10:15 AM To: JDzialo John Cc: [email protected]; AZabrecky Allan Subject: Re: HAProxy Hang during initial connection Hi John, On Tue, May 27, 2014 at 08:08:27PM +0000, JDzialo John wrote: > Hi Willy, > > Here is a capture of all traffic btwn the two servers using the host option. Thank you. > Basically traffic goes from haproxy to a web farm in a round robin fashion. > These individual web servers are accessing a single file server, (we > are in the process of splitting this file server into multiple servers > to spread the load). This one file server is getting slammed all day > with requests and that may be the root of the problem but have not > found the smoking gun necessary to prove it. > > Should I also get a capture btwn our web farm and the file server? > > I have also cc'd our network administrator to help come down to a solution. > > Let me know what you think and if there is anything else I can provide. > > As always thank you so much for your help. You have been a great help > to me in narrowing down issues. I spent some time reading the captures and found nothing abnormal in them. Do you have any indication of a faulty session or request ? Also I noticed that you took the captures on the server itself and that the server has TSO enabled since we're seeing large frames. It would be possible that there's a bug in the network driver or NIC causing some frames to be lost for example. Maybe the same trace taken on the haproxy server at the same time would reveal some extra information. Note, you don't need to post the whole file to the list, there are about 800 people who are probably not interested in receiving this 6MB file :-) Either you can put it on a public server, or you can simply send it privately to me. Thanks, Willy
