LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [CFT/PATCH] second try: backport of the RSthresholdlimitationpatch f

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [CFT/PATCH] second try: backport of the RSthresholdlimitationpatch for 2.4.x kernels
From: Roberto Nibali <ratz@xxxxxxxxxxxx>
Date: Mon, 23 Jun 2003 22:58:48 +0200
Tach Julius,

1 dr, 2rs, 1 client
added the -x option to the forward setup :
/sbin/ipvsadm -a -t 192.168.0.110:unrealircd -r 192.168.0.2 -g -w 1 -x 2
same to the other rs
the U threshold is 2, the L threshold is 0 <- for what is the L threshold?

The lower theshold is used to determine when a RS should be brought back into list of available servers to distribute the network load. This can be used to reduce load peak toggling and still have a RS back quite early. Imagine that you have 10 RS and they are equally equipped. You're serving a half-static and half-dynamic page. The RS bail out at let's say about 10000 conns each, but can easily handle 8500 conns. So in order to reduce the possibility of a cluster-down (all 10 RS are quiesced/not served anymore) which happens when you set the lower threshold to 0, you set it to something like 8500 so a quiesced RS is thrown back earlier into chain again. It's kind of a fast recovery from peak loads.

i can connect 6 times to the dr and get through round robin 3 connections to 
each rs
thought that U threshold is like max connections to the rs for a chosen service?

I should be :) Hmmm, what did I forget this time? Could you please send the output of ipvsadm -n --list --tresholds?

Thanks,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc

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