On Mon, Nov 25, 2002 at 06:02:19PM -0600, Andy Bakun wrote: > 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).
Err, no. MySQL prevents that looping as long as each server has a unique server-id. > 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 really the only > impediment to doing full two-way replication? That's the big limitation, yes. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 8 days, processed 268,724,961 queries (374/sec. avg) --------------------------------------------------------------------- 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
