LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Unwanted persistance

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Unwanted persistance
From: Chris Williams <chris.williams@xxxxxxxxx>
Date: 17 Oct 2002 15:58:55 +0100
Hey all,
I wrote sometime ago with a problem with persistance I was having, I
received good advice to rewrite the software to allow session affinity
which I did allowing me to abandon persistance all together. 

My setup is an LVS director hooking into 3 real servers serving
apache/tomcat4 w/session affinty.

Although I've now got a working system I have encountered a problem
whereby if I cut a real server down, ipvsadm takes the real server off
of its list but traffic still gets directed to the 'dead' real server.
LVS persistance is set to 0 so that's not the problem. After 2-5 minutes
requests stop being sent to the dead server and everything is hunky-dory
again.

I remembered this from a previous mail list question:
> > > Also setting persistance to 1 seems to affect the result for much more
> > > then 1 second, what exactly does this do?
> > 
> > don't know. You will have to wait for the TCP timeouts which are of the 
> > order
> > of 2mins in Linux (look at the connections with `netstat -an`)#

So maybe it is something to do with TCP timeouts? I checked out
/proc/sys/net/ipv4/tcp_keepalive_timeout but that was set to 7200 (2
hours,) which is far longer then the problem I am encountering.

2 minutes is too long to be throwing away requests, how can I improve
the speed so that when a real server drops out, no one (except me)
notices?

Thanks for all the help,
Chris.




This e-mail message is meant solely for the person or organisation to whom it 
is adressed. The message may contain personal or confidential information, or 
information that is not public in nature. Ehbas Ltd accepts no responsibility 
for message content and possible attachments that are unlawful or of 
questionable decency. Further dissemination, publication or duplication of this 
message is strictly prohibited if the person or organisation receiving this 
message is not the intended recipient. In the event that you are not the 
intended recipient, we request you to refrain from using the content and to 
immediately inform the sender of the error by returning the message. Thank you 
for your co-operation. 


<Prev in Thread] Current Thread [Next in Thread>