Hi, Lukas!

> On Wed, Jan 8, 2014 at 3:12 AM, Lukas Tribus <luky...@hotmail.com> wrote:
>> Hi,
>>
>>> Recently, we use haproxy1.5-dev21 in our product.And we want to get
>>> the benefit of http-keep-alive. But after we added the option
>>> http-keep-alive and deployed new version of haproxy. We found that the
>>> connection of FIN_WAIT_2 CLOSED ESTABLISHED increased quickly. when we
>>> change to the tunnel mode, it decreased.
>>
>> What release did you previously run? Please also specify your kernel release
>> and the output of "./haproxy -vv".
>>
>>
>>
>>> root@Haproxy01:~ # session-count.sh
>>> LISTEN 8
>>> FIN_WAIT_1 245
>>> FIN_WAIT_2 22836
>>> SYN_SENT 46
>>> LAST_ACK 943
>>> CLOSING 4
>>> CLOSE_WAIT 1151
>>> CLOSED 21940
>>> SYN_RCVD 11
>>> TIME_WAIT 255
>>> ESTABLISHED 13894
>>
>> But we don't know where does high numbers are, backend or frontend (or both;
>> equally distributed).
>>
>> Can you try (by matching your frontend port):
>>  netstat -nat | grep ":2001 " | wc -l

I calculated the connection in frontend and backend "direct".( as
freeBSD don't show port of 2001 in netstat -na when connect to
client.)

root@Haproxy01:~ # sh frontend_tcp_conns.sh
FIN_WAIT_1 129
FIN_WAIT_2 25729
LAST_ACK 1730
CLOSING 5
CLOSE_WAIT 1560
CLOSED 211
SYN_RCVD 33
TIME_WAIT 466
ESTABLISHED 13161

root@Haproxy01:~ # sh direct_tcp_conns.sh
FIN_WAIT_1 176
FIN_WAIT_2 244
SYN_SENT 1326
LAST_ACK 523
CLOSING 4
CLOSE_WAIT 1579
CLOSED 24321
TIME_WAIT 36
ESTABLISHED 7206

Reply via email to