|
Fernanda G Weiden wrote:
> Maybe you should look into a heartbeat cluster instead of a lvs one.
LVS fits here almost perfectly, whereas heartbeat almost at all doesn't
fit here (heartbeat will be used for LVS failover, though).
The traffic flow is as below:
realserver/origin1 \
- LVS -- client (internet)
realserver/origin2 /
Realservers are servers in the internet and their addresses will change
from time to time; client has to access them through the LVS address,
which will be permanent.
If you have an idea how heartbeat would help here, please clarify.
--
Tomasz Chmielewski
http://wpkg.org
> 2009/12/28 Tomasz Chmielewski <mangoo@xxxxxxxx>:
>> I have two real servers behind a balancer.
>>
>> I would like the balancer to forward all requests to the first real
>> server only.
>> Requests to the second balancer should go only if the first real server
>> has failed.
>>
>> I thought of assigning them different weights (i.e. the first server
>> would get a weight of 999999999; the second server would get a weight of
>> 1 - but still, it will make one request go to the wrong real server
>> every now and then).
>>
>> Is it possible to set up the balancer so that it sends request to one
>> real server as failover _only_?
>>
>> --
>> Tomasz Chmielewski
>> http://wpkg.org
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
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
|
