little theoretical question. I'm done setting up a bunch of 2-node MySQL 5.1 clusters user the control of several MMM instances.
We started some testing, joyously kill -9 the writer nodes and all went fine with the app chugging along, oblivious of the DBMS turmoils.
Then I thought, what if in production first server A goes down, server B takes over and more work is done, and finally B goes down as well.
If the sysadmin restarts the cluster first from A and later joins B while in the meantime work is done on the outdated data of A?
Does MySQL have a quorum mechanism that keeps A (or even B) in Recovery mode until it has decided what is the most recent transaction to continue from?
Thanks and apologies if it's an FAQ...