LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Failover with a high persistent timeout

To: "'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Failover with a high persistent timeout
From: Matthias Krauss <MKrauss@xxxxxxxxxxxxxx>
Date: Tue, 10 Sep 2002 20:06:21 +0200
Hello,
i've a easy test setup containing 1 Director on 3 Realservers, configured 
for direct routing - RoundRobin with equal weight and set a persistant 
timeout for 3 hours, this is "unfortunality" required through our M$ web
setup.

In addition i wrote a little failover app. running on a independant host,
which telnets to the Director and removes or set the weight to "0" 
if one of the RIP is in fail.

So far so good, if i set now a 3 hour pers. timeout and if a connection to 
eg RIP1 is established and if the RIP1 is in fail and if the RIP1 address 
are removed or weight to "0" then i see the RIP1 still in the IPVS
connection 
list counting down its long expire timeout. 
Doing ipvsadm -C clears most of the entries but RIP1 still shows up 
with "state NONE" and its high expire time even if the host was removed.

Is there a way to clear a particular host complete from the connection
table or another workaround ? (hope i missed nothing in the howto's)


Many many thanks in advance 
Matthias




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