|
Use the apropriate sysctl on the director :
net.ipv4.vs.expire_nodest_conn = 1
net.ipv4.vs.secure_tcp = 3
net.ipv4.vs.timeout_finwait = 2
net.ipv4.vs.expire_quiescent_template = 1
> -----Original Message-----
> From: lvs-users-
> bounces+francois.jeanmougin=123multimedia.com@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:lvs-users-
> bounces+francois.jeanmougin=123multimedia.com@xxxxxxxxxxxxxxxxxxxxxx] On
> Behalf Of sipieter nicolas
> Sent: Friday, October 21, 2005 11:40 AM
> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Subject: persistance problems
>
>
> i think i have a problem with the persistance option,
> here's how i invoked ipvsadm:
>
> [root@localhost ~]# ipvsadm
> IP Virtual Server version 1.2.0 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight
> ActiveConn InActConn
> TCP 192.168.123.1:http rr persistent 10
> -> 192.168.0.2:http Masq 1 0
> 0
> -> 192.168.0.3:http Masq 1 0
> 0
> [root@localhost ~]#
>
>
> the problem is, when i unplug one backend from the hub,
> because of persistance, clients get routed to the dead
> backend.
>
> say i unplug 192.168.0.2 while 192.168.0.3 is still ok
>
> because of round robin, client gets balanced
> one time to 192.168.0.2
> one time to 192.168.0.3
> one time to 192.168.0.2
> one time to 192.168.0.3 etc.. and so on.
>
> but if you unplug,say, 192.168.0.2 clients still gets
> routed to it despite it is unplugged from the hub, it
> cannot be accessed, but ipvsadm doesn't seems to see it.
>
> what could i do?
>
> thanks
>
>
> --------------------------------------
> Know more about Breast Cancer
> http://pr.mail.yahoo.co.jp/pinkribbon/
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
