Eric
Not being entirely au fait with ldirectord, I had a read of the source
code this morning and found the following which might (or might not)
help you out:
fork = yes│no
If yes, then ldirectord will spawn a child proccess for every virtual
server, and run checks against the real servers from them. This will
increase response times to changes in real server status in configura-
tions with many virtual servers. This may also use less memory then
running many seperate instances of ldirectord. Child processes will be
automaticly restarted if they die.
Default: no
I was going to suggest modifying ldirectord to fork health check
processes out for each VS, but Horms (or maybe Jacob) already did it :)
That should help. You'll end up with a lot of processes running but they
should be able to deal with the shorter check interval far better than
screaming through hundreds of checks every two seconds.
Graeme
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|