thanks for your answer. Meanwhile I could figure out some more things regarding the full sockets.
Willy Tarreau wrote:
>> As you can see the maxsockets limit gets nearly hit. If I look deeper >> into the sockets with netstat I can see that most connections go out to >> the http nodes. Thats about >11000 sockets!
Right, most where (>99%) in FIN_WAIT_2 state. On the other site (Debian Linux nodes) sockets where in LAST_ACK state.
>> So I think haproxy does not close all the sockets correctly or gets >> somehow in trouble with the FreeBSD sockets system. As for the moment >> I'll try to raise the maxsockets and see if the problem disappears.
That is exactly what I've done yesterday. I changed the following sysctl values:
Now a dead unused socket will get closed more quickly (less than a minute). This works fine, there are only a few connections left in the FIN_WAIT_2 state.
Here are my timeout settings in haproxy.conf:
Could these settings be the problem? What settings would you recommend?
-Matthias Received on 2008/04/29 11:33
This archive was generated by hypermail 2.2.0 : 2008/04/29 11:45 CEST