mysql - Master Master Replication with keepalived for failover & consistency -


i wanting setup master-master replication using mysql failover purposes. however, don't want data being accessed both masters can mitigate risks of master-master replication. have keepalived setup web server load balancing & failover purposes already. seem reasonable have keepalived pointing master , use master b in event master down, i.e. master b backup? have ideas better setup?

i not concerned speed as 0 downtime. thoughts on appreciated.

your idea fine, because database clients consistent results without risks of replication delays. when main node go down, clients again receive consistent result (in worst case of big replication delays see different data, still, consistent).


Comments

Popular posts from this blog

Email notification in google apps script -

c++ - Difference between pre and post decrement in recursive function argument -

javascript - IE11 incompatibility with jQuery's 'readonly'? -