On Sun, Sep 08, 2002 at 11:53:41PM +0000, Sam Przyswa wrote:
> Jeremy Zawodny (Jeremy@stripped) wrote:
> >
> >> 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?
>
> Thanks for the link, there is a lot of interesting things !
>
> >http://jeremy.zawodny.com/mysql/managing-mysql-replication_files/slide0121.htm
> >
> >Just make B a slave of A, C a slave of B, and A a slave of C.
>
> This is a good approach.
Except that it's fragile. One machine can go down and "break the
cycle" unforunately. :-(
> >Beware of using auto-increments in that scanario, though. You'll be
> >rather surprised and frustrated as explained in the manual.
>
> We are thinking about a parallel replication by use the Spread
> Toolkit (www.spread.org) to broadcast the writes queries on all the
> servers in the same time and only once with the guaranty that the
> messages are well received by each server, and load balance the read
> queries. Then we can have a very scalable clustering solution with a
> minimum network load.
Yeah, putting Spread support in MySQL for something like that might
not be a bad idea.
> What do you think about this concept, perhaps we can find a
> workaround for the auto-increment problem.
I've talked with two of the MySQL developers (Monty and Nick) about
solving auto-increment problem. After my Replication talk at OSCON
2002, we kicked around some ideas that seemed quit promising. I just
don't know when they'll be implemented. Hopefully Nick has them on
his TODO list. :-)
Jeremy
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
<Jeremy@stripped> | http://jeremy.zawodny.com/
MySQL 3.23.51: up 33 days, processed 671,775,990 queries (230/sec. avg)
