|
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 (-:
This is the most important problem, but there are many many more, and I
suggest people take a serious look at other options. Currently I use a
method of syncing 3 systems using BinLog's.
I think i'd best take this discuss to another forum.
Mike
> Michael McConnell wrote:
> > I know this is a little off topic. But here goes.
> >
> >
> >
> > Can anyone see a down side or a reason why one could not have two System
> > in a Failover Relationship running MySQL. The Database file would be
> > synchronized between the two systems via a crontab and rsync.
> >
> >
> >
> > Can anyone see a reason why rsync would not work? I've on many occasions
> > copied the entire mysql data directory to another system and start it up
> > without a problem.
> >
> >
> >
> > I recognize that there are potential problems that the rsync might take
> > place whil the master is writing and the sync will only have part of a
> > table, but mysql's new table structure is supposed to account for this.
> > If anything a quick myismfix should resolve these problems.
> >
>
> Why not just use MySQL's built in replication?
>
> --
> =======================================================================
> Paul J. Baker Internet Systems Developer
> pbaker@xxxxxxxxxxxxxxx Where2GetIt.com
> phone 847-498-0111x234
> fax 847-480-7422
> =======================================================================
>
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
