MySQL Master(Active) - Master(Active) Replication

Question

I am intending to use Master-Master (Active-Active) architecture of MySQL in my project. In my project I have two sites active and disaster site. On the active site, we do use 2 MySQL DB server - one is Master Active other is Master Passive which replicates data to Disaster site. Master Active also replicates to Master passive. All the three app servers write only on master active.

Now, I am planning to use Master Passive as Master active. Now, active site will have two master active and one app server will write on one master active and other two app servers will write on 2nd master active.

It would be great if you can enlighten the pros and cons of using this archirtecture. What issues may arise and what are the remedies for them ?

FYI.. Session stickiness is also used from web servers to app servers.

Thanks,

Prashant Gupta

Answer 1

What are you trying to achieve? Improved availability? Performance?

How do you plan to manage the connections from the app servers to the database instances? Floating IP addresses? Static mappings? What about failover? What monitoring do you have in place to measure availability of master nodes? Replication lag?