Re: MySQL Replication

["Michael McConnell" <michaelm@xxxxxxxxxxx>]

I do not see MySQL making any claims to Real-time. There are many situations
where a high load will result in systems getting backed up, especially if
your Slave system performs other operations.

MySQL's built in replication functions like so;
1. Master writes updates to Binary Log
2. Slave checks for Binary Updates
3. Slave Downloads new Bin Updates / Installs

Correct?

Mike


> Michael McConnell wrote:
> >
> > Keep in mind, there are no *real time* replication methods available for
> > MySQL. Running with MySQL's building Replication commonly results (at
least
> > with a 6 gig / 400 megs changing) in as much as 1 hour of data
> > inconsistency. The only way to get true real time is to use a shared
storage
> > array.
> >
>
> MySQL builtin replication is supposed to be "realtime" AFAIK. It should
> only fall behind when the slave is doing selects against a database that
> causes changes to wait until the selects are complete. Unless you have a
> select that is taking an hour, there is no reason it should fall that
> far behind. Have you discussed your findings with the MySQL developers?
>
> --
> =======================================================================
> 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
>