Hi Mark, The tree you just merged into trunk was a multi-master enabled tree. I.e., a single slave can receive events from more than one master (single direction but multiple channels). I believe what Brian is looking for is normal bi-directional master to master replication.
We haven't made any real improvements in the master to master scenario, so your statements are still valid, though. There is still no conflict resolution and it's something that still needs testing. Dave On Jul 9, 2011, at 1:31 AM, Mark Atwood <[email protected]> wrote: > Master Master Replication is now back in the main tree. It could use > some heavy testing. It has no conflict resolution, the application > will be responsible at a higher level to make sure that primary keys > are unique, etc. > > ..m > > On Fri, Jul 8, 2011 at 7:39 AM, Brian Moon <[email protected]> wrote: >> Hi all, >> >> I have a new project coming up and thinking about the solution. I was >> wondering if any work had been done with master to master replication and >> conflict resolution in Drizzle. It is very easy to break it in MySQL. Simply >> shut down a slave for a few seconds on just one side and everything goes to >> crap. Is this any better in Drizzle? Is master to master even supported? >> >> -- >> Brian. >> http://brian.moonspot.net >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~drizzle-discuss >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~drizzle-discuss >> More help : https://help.launchpad.net/ListHelp >> > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
