Documentation Home
MySQL Utilities 1.5 Manual
Related Documentation Download this Manual
PDF (US Ltr) - 1.5Mb
PDF (A4) - 1.5Mb
HTML Download (TGZ) - 289.5Kb
HTML Download (Zip) - 301.7Kb

8.7.3 Target Configuration

The two physical hosts are host1.localdomain ( and host2.localdomain ( It is recommended that you do not rely on an external DNS service (as that is an additional point of failure) and so these mappings should be configured on each host in the /etc/hosts file.

A single Virtual IP (VIP) is shown in the figure ( and this is the address that the application connects to when accessing the MySQL Fabric. Pacemaker is responsible for migrating this between the two hosts.

One of the final steps in configuring Pacemaker is to add network connectivity monitoring in order to attempt to have an isolated host stop its MySQL services to avoid a split-brain scenario. This is achieved by having each host ping an external (not one part of the cluster) IP addresses - in this case the network router (

All the necessary software (i.e. binaries) must be installed in a regular partition, independent on each node. MySQL socket (mysql.sock) and process-id ( files are stored in a regular partition as well. The MySQL Server configuration file (my.cnf), the database files (data/*) and the MySQL Fabric configuration file (fabric.cfg) are stored in a DRBD controlled file system that at any point in time is only available on one of the two hosts.

Figure 8.1 MySQL Fabric Setup using DRBD and Pacemaker

MySQL Fabric Setup using DRBD and Pacemaker

User Comments
Sign Up Login You must be logged in to post a comment.