|
We're using lvs-kiss which is supposed to handle no response from the web
server and route to the one that's up, correct? I think ipvsadm reads from
this file as well as takes note to which one is responding?
Our lvs-kiss.conf file looks like this:
<VirtualServer 210.210.30.200:80>
ServiceType tcp
Scheduler wlc
# should it be dynamic or static?
DynamicScheduler 1
Persistance 600
QueueSize 2
Fuzz 0.1
<RealServer 210.210.30.210:80>
PacketForwardingMethod gatewaying
Test webtest.pl --url http:// 210.210.30.210/
</RealServer>
<RealServer 210.210.30.211:80>
PacketForwardingMethod gatewaying
Test webtest.pl --url http:// 210.210.30.211/
</RealServer>
</VirtualServer>
If 210.210.30.210 goes down or doesn't respond, I was assuming all requests
would go to .211? Isn't that the whole point of using LVS?
Kirk
-----Original Message-----
From: Mack.Joseph@xxxxxxxxxxxxxxx [mailto:Mack.Joseph@xxxxxxxxxxxxxxx]
Sent: Monday, March 28, 2005 9:13 AM
To: kirk@xxxxxxxxxxxxxxxxx; LinuxVirtualServer.org users mailing list.
Subject: RE: Initial setup
Joseph Mack PhD, High Performance Computing & Scientific Visualisation
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007 Federal
Infrastructure Contact-Ravi Nair 919-541-5467 - nair.ravi@xxxxxxx,
Federal Visualization Contact - Joe Retzer, Ph.D. 919-541-4190 -
retzer.joseph@xxxxxxx
lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx wrote on 03/28/2005 11:49:46
AM:
> So I then shut down apache on www_farm1 to make sure
> source1 gets a response
> from www_farm2, but that's where it breaks. Whichever one
> I shut down, the
> cooresponding source comes back with a connection refused.
do you remove the corresponding entry with ipvsadm?
Joe
|
