| 1 |
********************************** |
| 2 |
JK> Maybe you can just use two A records in your dns. |
| 3 |
|
| 4 |
JK> Both point to one server, and both servers keep an eye on the other with |
| 5 |
JK> hearthbeat, |
| 6 |
|
| 7 |
JK> As soon as one of the servers gets unresponsive the other claims the ip |
| 8 |
JK> as a secundary ip. |
| 9 |
|
| 10 |
JK> ifconfig eth0 add otherip. |
| 11 |
JK> // not forget to arp for it! |
| 12 |
|
| 13 |
JK> And as soon as the hearthbeat finds the other server to be back online, |
| 14 |
JK> it unsets the ip, and lets the other know that it can add the ip again. |
| 15 |
|
| 16 |
JK> Not so hard, just a couple of shell scripts afaik. |
| 17 |
|
| 18 |
JK> greets |
| 19 |
JK> Jan |
| 20 |
|
| 21 |
********************************** |
| 22 |
|
| 23 |
This sounds pretty good, but the customer is running mysql with data |
| 24 |
changing all day long. That means that I would have two seperate db, |
| 25 |
one on each machine, without being able to merge/keep uptodate those |
| 26 |
dabatases :/ |
| 27 |
|
| 28 |
Best regards, |
| 29 |
|
| 30 |
Benjamin MALYNOVYTCH |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
gentoo-cluster@g.o mailing list |
Archives