Mysql Master Master Replication Issue -


i implementing master master replication in mysql. can have doubt.

for case, there 2 solution 1. use 1 master failover cases only. (i dont recommend) 2. distribute load changing application (like it)

issue found in of 2 approach.

we have 2 masters , b. user update city delhi , goes server , before b replicate query server goes down , shift queries server b only. same user updates city mumbai. when server goes up, * delhi update query go server b (bin log reading) * mumbai update query go server (bin log reading)

hence discrepancy in data.

how solve issue ?

my database mix of innodb , myisam

i guess (not tested) can achieve proxy, e.g. maxscale

configure proxy readsplit distrubutes reads on server , b , 1 master rest. in addition setup master failover scenario when server goes down.

actually have simple master-slave setup in maxscale, in background there still master-master working. maxscale or application doesn't need know this.


Comments

Popular posts from this blog

java - UnknownEntityTypeException: Unable to locate persister (Hibernate 5.0) -

python - ValueError: empty vocabulary; perhaps the documents only contain stop words -

ubuntu - collect2: fatal error: ld terminated with signal 9 [Killed] -