Configuring a production environment using a pair of MySQL servers in a Master/Fail Over Master situation is a common process to provide many benefits including supporting failover, backup/recovery, higher availability for software & database upgrades. This is also a common method for database shards. One of the key hidden benefits is by performing regular controlled failovers for example with software upgrades you are actively testing your disaster recovery procedures. Most organizations have a partial plan, some don’t have any, but rarely do people test their disaster recovery.
There is no one way to configure and manage such an environment. There are a number of options including:
- Develop your own home grown scripts
- Flipper by Proven Scaling
- MMM by Percona
- Heatbeat by the Linux High Availability Project
I have started a detailed review of a number of these technologies and will be providing my findings for review.
This is not the only way to solve the problems of course. Google for example have provided MySQL Patches that include features such as semi-sync replication and mirrored binary logs. Red Hat Cluster suite, and MySQL/DRBD are other technologies but less idea for various reasons specifically the “cold” nature of the failover environment.
Ronald, just my $.02: I’m sure you realize that MySQL/DRBD works in conjunction with Heartbeat/Pacemaker; it makes no sense to deploy DRBD in a MySQL environment without a cluster management framework. Also, I don’t see how Red Hat Cluster Suite provides any more or less “cold” standby than Heartbeat/Pacemaker; they follow pretty much exactly the same principles.
Hi Ronald,
At Percona we have a lot of ideas for improving MMM, Baron recently wrote this recently.
http://code.google.com/p/mysql-master-master/wiki/DevelopmentPlans
Basically it lacks a lot of features and has some “interesting” behavior, perhaps whilst you are evaluating all these technologies you could help us add to MMMs wishlist.
Cheers,
Ewen
Great! I’m looking forward to your findings.