> The benefit comes when your active master dies and mmm switches to the passive one
> without (hopefully!) your app even noticing
Stop the presses, sold. This will save me not only a lot of time implementing this
structure but also allows me to actually sit back and relax if the master stops working.
With the regular master-slave, if the master somehow crashed I manually had to change the
web server writing db ip from master to slave, this with people shouting at your ears 'no
records are getting saved!!'
Thanks a lot for the info, will try to implement this tomorrow!!!