CV> Only queries that succeed on the master server are ran on the CV> slave. If a query that succeeded on the master fail on the slave, CV> replication will be halted until the problem is manually resolved CV> I think.
Very true. Unfortunately, there are a number of "shouldn't fail" queries that will kill replication. My pet peeve with MySQL replication is that ALTER TABLE queries will NOT replicate, so the first query after one that references a changed field with shut down replication. THIS IS NOT DOCUMENTED, as far as I've found. One of my clients does this regularly; I have to figure out WHAT they changed, in the order they changed it, and propagate the changes to the two slaves. This week, he modified one table five times, deleted it, recreated it with changes, then modified it twice again... I had to restart the slave process several times, so that it could move up to the next modification query. I have a CRON job that emails me the status of replication on all servers every hour... -- Jeff Brenton President, Engineered Software Products, Inc http://espi.com Questionable web page: http://dididahdahdidit.com Liberalism grants you the freedom to advocate any idea*. * Please see http://www.dididahdahdidit.com/except.php for a current list of exceptions
