Pacemaker's best-kept secret: crm_report
Posted on Sat 30 January 2016 in hints-and-kinks • Tagged with Pacemaker • 3 min read
Pacemaker has an excellent, but little-known, error reporting facility: crm_report.
Continue reading
Posted on Sat 30 January 2016 in hints-and-kinks • Tagged with Pacemaker • 3 min read
Pacemaker has an excellent, but little-known, error reporting facility: crm_report.
Posted on Tue 04 December 2012 in hints-and-kinks • Tagged with Galera, MySQL, Pacemaker • 1 min read
Once you have one instance of Galera running, and it is running on the same node that holds the temporarily-configured cluster IP (192.168.122.99 in our example), you can add your resources to the Pacemaker cluster configuration.
Create a temporary file, such as /tmp/galera.crm
, with the …
Posted on Tue 04 December 2012 in hints-and-kinks • Tagged with Galera, MySQL, Pacemaker • 1 min read
In order to bootstrap your Galera cluster, manually bring up the cluster IP address on the desired interface. In this example, we’ll use 192.168.122.99 and eth1:
ip address add 192.168.122.99/24 dev eth1 label eth1:galera
And initialize the Galera cluster:
mysqld --wsrep_cluster_address …
Posted on Tue 04 December 2012 in hints-and-kinks • Tagged with Galera, MySQL, Pacemaker • 2 min read
You now need configure Corosync. The following example configuration file assumes that your cluster nodes have two network interfaces, using the 192.168.122.0/24 and 192.168.133.0/24 networks. You will need to adjust this to your own network configuration.
Set the contents of /etc/corosync …
Posted on Tue 04 December 2012 in hints-and-kinks • Tagged with Galera, MySQL, Pacemaker • 2 min read
If an entire node happens to get killed, and that node currently does
not hold the Galera IP (192.168.122.99 in our example), then the other
nodes simply continue to function normally, and you can connect to and
use them without interruption. In the example below, alice
has …