I have successfully configured two mysql instances to replicate to each other (According to /doc/en/Replication_Features.html, it is possible to do it in a A->B->C->A relationship, but I only did it with two servers and I don't have log-slave-updates on (I think if I did, it would immediately stop the slave thread as the updates get caught in a loop).
FYI, I'm using a self-compiled RPM of 3.23.51 on Linux 2.4. All my tables are InnoDB. It's very slick, updates on either server get propagated to the other server. I have not stress tested it yet, and my (simple) application only does updates to a single server at a time. The only problem is the auto_increment columns in the tables. Updates that occur on both machines at the same time, that generate the same auto_increment value, causes the slave threads to die: and rightly so. I can, of course, program my application to generate non-conflicting, server independant key values without the need for the auto_increment, but has anyone had any experience with this? Is this the only impediment to doing full two-way replication? What other 'data corruption' or 'out of sync' issues are there to worry about? Andy. [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
