Active-active replication is available and is in use.
The main think to bear in mind is that there is some effort required on your part if you
want MySQL Cluster to handle the conflict detection or resolution (conflict=the same row
being updated on both sites at about the same time). For example, you'd need to include an
integer timestamp column in each of the tables where conflicts need to be handled and
maintain that at the application layer. There are also some limitations on its use (for
example, if using conflict resolution it backs out the change to the row where the
conflict occurs but not the rest of the transaction).
This post walks through setting up active-active (multi-master) replication between 2
MySQL Cluster deployments...
Note that it doesn't explain how to use the conflict detection/resolution - for that,
Known limitations of MySQL Cluster replication are documented at
Andrew Morgan | MySQL Senior Product Manager
ORACLE Corporation UK Ltd is a company incorporated in England & Wales | Company Reg.
No. 1782505 | Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA
Oracle is committed to developing practices and products that help protect the environment
> -----Original Message-----
> From: Erez Epstein [mailto:erezep@stripped]
> Sent: 15 July 2010 14:33
> To: cluster@stripped
> Subject: Active Active Cluster
> i have heard on many issued for the bad and good , about active active,
> and as I'm designing a new project, would like to know if the latest
> of mysql support active active cluster fully,
> and that there are no know issues?
> is it difficult to maintain such a platform?
> Show My Ip <http://www.showmyip.me>