Maybe you can just use two A records in your dns.
Both point to one server, and both servers keep an eye on the other with
hearthbeat,
As soon as one of the servers gets unresponsive the other claims the ip
as a secundary ip.
ifconfig eth0 add otherip.
// not forget to arp for it!
And as soon as the hearthbeat finds the other server to be back online,
it unsets the ip, and lets the other know that it can add the ip again.
Not so hard, just a couple of shell scripts afaik.
greets
Jan
Benjamin MALYNOVYTCH wrote:
**********************************
MB> You're faced with an impossible requirement here:
MB> If, as you've stated "one machine is not enough due to high trafic" a
MB> single machine left over after a filure WON'T be able to keep you going.
MB> For a high availability setup, you need a configuration where the
MB> remaining node(s) after failure are still powerfull enough to carry on.
MB> Bye, Martin
**********************************
Well, one machine is enough most of the time. It only slows down
sometimes, due to high trafic. That's why this cluster would be fine
enough, letting us enough time to restart the failling machine.
Is this configuration still possible ?
Best regards.
Benjamin.
--
[email protected] mailing list
