This handles part of the problem but a true load balanced master solution is needed. There's no real advantage in spending 5, 10 or $20,000 on a failover master if you can't load balance and the spare will just sit idle. Master servers should intelligently talk to each other and determine duplicate key problems.
You could create an LVS cluster of masters. You would have to write some hand code to remove a master from the cluster when it is behind so when a master is brought back up, it's out of the cluster until it has caught up. Then toss in some code to sync the downed master with the current running ones. Perhaps you could point replication to the LVS IP instead of a specific machine. When it comes back up, it will find a valid master to connect to via LVS, replicate, and then rejoin the collective... err, cluster. :) If a host that is currently being a master to another master goes down, the slave to that master will reconnect to LVS and find a new host to get data from. This still leaves the auto_increment problem. On the slave side however, it's easy. You can build a cluster of slaves and probably create a nice script to change weight based upon distance behind the master. After a slave falls "so far" behind, it's removed until it catches back up. More thoughts are always welcome. -J -----Original Message----- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]] Sent: Saturday, September 07, 2002 10:51 PM To: Sam Przyswa Cc: [EMAIL PROTECTED] Subject: Re: Replications... On Sun, Sep 08, 2002 at 03:30:35AM +0000, Sam Przyswa wrote: > Jeremy Zawodny ([EMAIL PROTECTED]) écrivait: > > > >On Fri, Sep 06, 2002 at 03:52:24PM +0000, Sam Przyswa wrote: > >> Hi, > >> > >> Does the next MySQL 4.x version will support cross replications > >> between several master servers in cluster ? > > > >Multi-master replication works as well in 4.x as it does in 3.23.xx. > > Does multi-master mean master to master, imagine you have 3 MySQL > servers, A, B, C, with a load balancer in front end, if we make an > update on A, is it possible to replicate/sync the change on B and C > ? You want to do this? http://jeremy.zawodny.com/mysql/managing-mysql-replication_files/slide01 21.htm Just make B a slave of A, C a slave of B, and A a slave of C. Beware of using auto-increments in that scanario, though. You'll be rather surprised and frustrated as explained in the manual. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 32 days, processed 662,833,682 queries (233/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 --------------------------------------------------------------------- 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
