topic networking fin_wait_2 in Operating System - HP-UX

networking fin_wait_2

System Unix — Wed, 26 Dec 2007 10:54:30 GMT

Hi,

fin_wait_2_timeout is defined as 0 on one of the servers rp8420 OS version 11.11. currently there are ~1600 connections in fin_wait_2 status.
is there any limit in connections ?
is there any infuence from any kind on the performance of the server ?

please advise,

thanks,

Reuven

Re: networking fin_wait_2

Murat SULUHAN — Wed, 26 Dec 2007 19:10:39 GMT

Hi Reuven

From official docs
TCP FIN WAIT 2 Timer

The ndd TCP parameter tcp_fin_wait_2 determines how long a TCP connection will be in FIN_WAIT_2.

Normally one end of a connection initiates the close of its end of the connection (indicates that it has no more data to send) by sending a FIN. When the remote TCP acknowledges the FIN, TCP goes to the FIN_WAIT_2 state and will remain in that state until the remote TCP sends a FIN.

If the FIN_WAIT_2 timer is used, TCP will close the connection when it has remained in the FIN_WAIT_2 state for the length of the timer value.

The FIN_WAIT_2 timer must be used with caution because when TCP is in the FIN_WAIT_2 state the remote is still allowed to send data. In addition, if the remote TCP would terminate normally (it is not hung nor terminating abnormally) and the connection is closed because of the FIN_WAIT_2 timer, the connection may be closed prematurely.

Data may be lost if the remote sends a window update or FIN after the local TCP has closed the connection. In this situation, the local TCP will send a RESET. According to the TCP protocol specification, the remote TCP should flush its receive queue when it receives the RESET. This may cause data to be lost.

Default: 0 (indefinite)

Range: 0 - 2147483647

Units: Milliseconds

So you should query why your clients send RESET to server instead of FIN?.

Each FIN_WAIT_2 connection needs memory so you can define a timeout value with ndd

Best Regards
Murat

Re: networking fin_wait_2

System Unix — Wed, 26 Dec 2007 21:26:53 GMT

thanks Murat :-)

Reuven

Re: networking fin_wait_2

rick jones — Mon, 31 Dec 2007 19:26:11 GMT

If there is no more socket associated with each of those FIN_WAIT_2 connections, the tcp_keepalive_detached_interval stuff, should (IIRC) be culling those connections, unless there is still a TCP endpoint at the other end, responding to the keepalive probes...

Re: networking fin_wait_2

System Unix — Tue, 01 Jan 2008 06:41:51 GMT

tnx, Rick