DRBD and MySQL - Heartbeat Setup
Feb 12, 2010, 06:03 (0 Talkback[s])
(Other stories by Sean Hull)
"Heartbeat automates all the moving parts and can work as well
with the MySQL master-master active/passive solution as well as it
can with the MySQL & DRBD solution. It manages the virtual IP
address used by the database, directs DRBD to become primary, or
relinquish primary duties, mounts the /dev/drbd0 device, and
starts/stops MySQL as needed.
"DRBD provides an alternative high availability solution for
MySQL. By effectively putting a mirrored filesystem beneath the
database, the Linux operating system is thus replicating all of
your data without the database even knowing about it. In our first
two articles on the topic, we discussed some of the strengths and
weaknesses of native MySQL statement based replication and then
compared and contrasted those with the DRBD based solution. The
advantages are in simplification of management, and elimination of
some of the anomalous behavior of MySQL replication. The potential
tradeoffs though are some performance impact, both in how your
filesystem will then respond as it has to wait for acknowledgement
of writes on remote destinations as well as a performance hit when
you failover as the target MySQL database is starting up fresh, and
has to warm its cache before performance will equal that on the
former primary."
Complete Story
Related Stories: