Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have set up normal (non-clustered, ndb) two server Mysql Master-Master replication for high availability. Each server has an application that can update the local database, the changes propagate to the other database via replication.

It is possible that both applications can do an update on the same data item, with the newer one overwriting the older during the replication process. Mysql Cluster solves this problem with a "same value wins" conflict resololution set-up.

Is it possible to setup similar or same conflict resolution rules for non-cluster (ndb) replication?

share|improve this question
add comment

1 Answer

So, after days of investigation it looks like the answer is 'No' - Mysql replication does not support update conflict resolution options like they are available with Mysql cluster. I just wasn't able to find a single setting or option that would point in the right direction.

Unfortunately Mysql Cluster wasn't an option for me because it requires 3 servers (2 workers, one admin) as a minimum and I am running a 2 server system.

I did investigate semi-synchronous replication (MySQL 5.5) but this didn't have any better conflict resolution either.

In the end I had to go back and re-conceive the application to minimise/avoid the risk of conflict.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.