|
On Wed, Jun 28, 2006 at 04:41:29PM +1000, Jason Downing wrote:
> I'm talking about existing connections. I'm pretty sure new connections are
> absolutely fine, but I will test this to make sure, thanks for reminding
> me. I am not using persistence (although I have tried it and results were
> the same).
Ok, if it is existing connections that are the problem, then this is
an expectied behaviour, which can be changed using
/proc/sys/net/ipv4/vs/expire_nodest_conn
expire_nodest_conn - BOOLEAN
0 - disabled (default)
not 0 - enabled
The default value is 0, the load balancer will silently drop
packets when its destination server is not available. It may
be useful, when user-space monitoring program deletes the
destination server (because of server overload or wrong
detection) and add back the server later, and the connections
to the server can continue.
If this feature is enabled, the load balancer will expire the
connection immediately when a packet arrives and its
destination server is not available, then the client program
will be notified that the connection is closed. This is
equivalent to the feature some people requires to flush
connections when its destination is not available.
> I will try a 2.6 kernel and let you know the results. It will take me a
> while to do because my previous limited experience of changing kernels has
> always resulted in considerable head scratching....
I'm pretty sure you will get the same result, now that I think
its related to expire_nodest_conn.
> I also have found out that there is a 60 second timeout in tomcat cluster
> to declare a node dead. I am currently checking to see how to change this
> to 2 seconds.
--
Horms
H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/
|
