|
Thanks for your response,
I tried with the last version of ldirectord, but the result is the same.
I have noticed there was a problem when i tried to add request and receive
tests
on the same line than the real server IP (real=10.1.1.25:80 masq 1
"/test.htm" "test").
So i added that request and receive tests on another line.
Is there a similar problem with the weight parameter?
Regards
-----Message d'origine-----
De : Horms [mailto:horms@xxxxxxxxxxxx]
Envoyé : mardi 5 juillet 2005 11:25
À : Stéphane Klein; LinuxVirtualServer.org users mailing list.
Objet : Re: Weight problem
On Tue, Jul 05, 2005 at 10:42:07AM +0200, Stéphane KLEIN wrote:
> Hi,
>
> I'm using lvs load balancers for web applications.
> Kernel version: 2.6.10
> Cluster Management: Heartbeat 1.2.3
> Job scheduling algorithm: wlc
> Cluster's type: LVS/NAT
> Monitoring daemon: Ldirectord 1.77.2.5
>
>
> I have two web servers with differents processors. I try to implement
> different weight for that servers.
> So, here is ldirectord configuration file:
>
> checktimeout=8
> checkinterval=5
> virtual=xxx.xxx.xxx.xxx:80
> protocol=tcp
> scheduler=wlc
> persistent=900
> real=10.1.1.25:80 masq 1
> real=10.1.1.26:80 masq 3
> checktype=connect
> service=http
>
> The ipvsadm -Ln result is:
>
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP xxx.xxx.xxx.xxx:80 wlc persistent 900
> -> 10.1.1.26:80 Masq 1 2 30
> -> 10.1.1.25:80 Masq 1 2 2
>
> You can see that the weight is not correct.
> An idea?
Hi,
1.77.2.5 is a pretty old version of ldirectord, and there have been many
fixes. The current CVS version, 1.77.2.20 (also known as 1.108), does
not exhibit this behaviour, you can get it from cvs or cvsweb, as per
the instructions at http://www.vergenet.net/linux/ldirectord/cvs.shtml
N.B: this version does have a bug in the https (not http) check,
I hope to have a fix in CVS shortly.
--
Horms
|
