|
Hi Simon,
thanks for the hint. You are right, ldirectord is starting standalone
from init. Within the next maintenance circle I plan to add more
resources to the loadbalancer and then I will realize the new starting
methode (to get less checks and a pretty log file as a bonus ;-) ).
Gerd
-----Ursprüngliche Nachricht-----
Von: Simon Horman [mailto:horms@xxxxxxxxxxxx]
Gesendet: Dienstag, 24. April 2007 05:28
An: it-intuition
Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Betreff: Re: ldirectord double checks url
On Fri, Apr 06, 2007 at 12:32:50AM +0200, it-intuition wrote:
> Hello,
>
> I run a two node loadbalancer with ldirectord (version 1.2.5-1) and
> heartbeat (version 1.2.5-1) on Debian Sarge for several months now.
> Now I discovered that the first node always sends two requests to our
> webservers and the second node only sends one request. Does this issue
> belong to my outdated versions of ldirectord+heartbeat (I know I
> should update to version 1.2.5-3 ...) or did I misconfigure the hole
> thing? Anyhow, the loadbalancer acts as expected.
How are you starting ldirectord. If you have it listed in linux-ha's
haresorces file, then it should only run on the active node and you
shouldn't see the connection duplication that you observed. If you run
ldirectord standalone from init then you will.
I personally don't think that extra checks are a problem. But if they
bother you, try the haresources approach.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
|
