On Mar 3, 2014, at 10:46 49, Cowboy <c...@cwf1.com> wrote: > If you were so inclined, you could check and compare the timestamps > on the files in /var/lib/mysql/databasename/tablename.MYI between the > two ( or three, or... ) machines and know which is the most recent
No, No, NO - you do *not* want to do this! MySQL makes extensive use of internal file caching as a technique for boosting performance. The only time that the timestamps on the actual files can be taken as indicative of the true state of things is after doing a FLUSH TABLES WITH READ LOCK call (perhaps — InnoDB tables can get you in trouble here) or ideally if the mysqld(8) daemon is shut down. A setup where two MySQL instances update each other is known as ‘active-active replication’. It can be done, but it requires careful application design to ensure that updates to a particular table are wholly confined to one or the other of the instances (a technique known as ‘data sharding’). The consequence of violating this rule can be data collisions in things like column auto-increment values, which in turn will halt replication and require manual intervention to recover from the inconsistent state. Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | Like the ski resort of girls looking for husbands and husbands looking | | for girls, the situation is not as symmetrical as it might seem. | | -- Alan McKay | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
