|
Michael McConnell wrote:
There are many fundamental problems with MySQL Replication.
MySQL's Replication requires that two systems be setup with identical data
sources, activate in a master / slave relationship. If the Master fails all
requests can be directed to the Slave. Unfortunately this Slave does not
have a Slave, and the only way to give it a slave, it turn it off
synchronize it's data with another system and then Activate them in a Master
/ Slave relationship, resulting in serious downtime when databases are in
excess of 6 gigs (-:
What is the downtime when you have to run myisamchk against the 6 gig
database because rsync ran at exactly the same time as mysql was
writting to the database files and now your sync'd image is corrupted?
There is no reason you can not set up the slave as a master in advance from the
beginning. You just use the same database image as from the original master.
When the master master goes down, set up a new slave by simple copying
the original master image over to the new slave, then point it to the
old slave that was already setup to be a master. You wouldn't need to
take the original slave down at all to bring up a new one. You would
essentially be setting up a replication chain but only with the first 2
links active.
-Paul
|
