|
On Tue, 14 Oct 2003, SB CH wrote:
> >The default timeout values are fine. You can use "ipvsadm -Lcn" to list
> >the connections at the load balancer when there is no connection at the
> >servers, most likely those connections will be expired soon (see the
> >expire value).
>
> >If you stick to that connections will be expired at almost the same time
> >that they are expired in the servers, you can use
> >"cat /proc/sys/net/ipv4/tcp_fin_timeout" at the server to see the timeout
> >value, then set the same timeout value at the load balancer by "ipvsadm
> >--set 900 <tcp_fin_timeout> 300".
>
>
> So thanks for your answer.
> But my concern is "ESTABLISHED" state and I guess that timeout is 15
> minutes now,
> So when I use wlc schedule algorithm, there are some problems because so
> long established state timeout, in spite of the no connection.
>
It's weird that your server has already closed the connection, but the
connection at load balancer still remains in the "ESTABLISHED" state. I
don't have ideas on it. Can you caputre some packets on how a connection
is established and closed using ethereal or tcpdump?
Regards,
Wensong
|
