Re: MySQL Master(Active) - Master(Active) Replication
Posted by:
Irfan Ali
Date: September 26, 2012 03:32PM
I don't what are the intentions of doing this.
Anyways, writing to multiple masters in active-active topology is not recommended becuase it can raise many glictch which are near to impossible to resolve in case of replication errors.
1) Prevent auto-increment collisions. Like store even id's on master 1 and odd id's on master 2 but it will leaves gaps between auto increment.
2) It can raise silent replication errors. e.g.
master1> UPDATE test SET col1=2 WHERE col2=2; --app1
master2> UPDATE test SET col1=3 WHERE col2=2; --app2
Nor of the master has reliable data.
3) Also you need to handle UNIQUE constrainst from application logic. For example, username via registeration.
Subject
Views
Written By
Posted
6218
September 24, 2012 09:18AM
1858
September 24, 2012 06:32PM
1780
September 24, 2012 11:34PM
Re: MySQL Master(Active) - Master(Active) Replication
1888
September 26, 2012 03:32PM
1669
September 27, 2012 02:01AM
1464
September 27, 2012 07:59AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.