Hi Luca, On Mon, Jun 22, 2009 at 01:38:53PM +0200, Luca Pimpolari - Multiplayer wrote: > Hi to all, > > I'm using haproxy to serve our web infrastructure, it serves about > 500/600 concurrency connection, with some peak to 1000/1200 > concurrency connection. > All work great, and performance are also so good, but sometimes > haproxy stop to serve http traffic (mode http),instead other kind of > traffic continues to work (mode tcp). > > I'm using haproxy 1.3.18, i attach configuration file. > Kernel on machine is 2.6.26-2-686 on debian 5.0 > > Stops are sudden, and i'm unable to replicate it. When it happens > haproxy daemon is still up, and continue to serve other kind of > service (mode tcp), also stats stop to work. > > Any help ?
I see that you don't have any "timeout client" in either your "defaults" section nor your frontends. So most likely after some users have failed to properly disconnect, all you connections are saturated and you cannot serve anybody anymore. And by the way, only one of your backends has timeouts, so I really suggest that you set them all in your defaults section. Also, please be careful, I see very large timeouts here. 330s for a server response in HTTP is way too long, nobody will wait that long! And having that for a health check or a connect is inappropriate too ! A typical connect timeout is around 5s. A client/server timeout depends on the application but we generally see between 10 and 60s. Regards, Willy
