Another method, though maybe we're going crazy here, is to use DRBD and
heartbeat.
DRBD will write your mysql changes to two machines, and heartbeat will
manage the IP and mysql.
Gord
--
Arboreta Internet Services
Gord Fisch
http://www.arboreta.ca
skype: gord.fisch
land: 514-481-8524
cell: 514-969-9928
On 01/18/2011 11:41 AM, David Filion wrote:
On 1/18/2011 9:47 AM, Stephane Bakhos wrote:
Set the timeout to near 0 and have mysql_connect retry on the other on
failure.
OR
Set a haproxy in front of the MySQL servers to connect to whichever one
responds.
The apps in question are vbulletin and wordpress sites so I can only
specify one target server. That's why I was thinking master/slave.
Point them to the floating ip and if the server holding the ip crashes
move the ip to the other server. The problem as I mentioned is the
mysql clean up afterwords is messy and highly manual.
I guess I could always go master/master and still move the mysql ip
address from one server to the other.
This is for a half dozen _low_ traffic sites so I don't want to go
crazy, I just want redundancy.
David
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
