On 2011-10-22 20:33, Michael Marrotte wrote:
I have a 2-node MySQL master/slave to master/slave setup and am looking
to add a MySQL "health" check that can take a node out of the cluster if
its slave is unhealthy, e.g. out of sync. The master/slave master/slave
config is working fine, hence writ
Raoul:
I made some progress... The default location of the relay-log and log-bin
weren't matching up. So, when I specify them things worked out -- now
Pacemaker is starting my mysql instances and replication is working -- that
is, master/slave... Next hurdle is master/slave <-> master/slave.
T
When I CHANGE MASTER TO MASTER_HOST='' on both nodes, I can get a
master/slave in pacemaker, as follows:
Last updated: Sat Oct 22 13:17:26 2011
Stack: Heartbeat
Current DC: vsaas-test-web-2 (b06e9042-c6a8-4acd-b81e-23728214a30a) -
partition with quorum
Version: 1.0.8-042548a451fce8400
hi!
On 22.10.2011 20:33, Michael Marrotte wrote:
primitive p_mysql ocf:heartbeat:mysql \
params binary="/usr/sbin/mysqld" config="/etc/mysql/my.cnf"
replication_user="slaveuser" replication_passwd="slavepw"
test_passwd="root" pid="/var/run/mysqld/mysqld.pid"
socket="/var/run/mysqld/mysqld.s
I have a 2-node MySQL master/slave to master/slave setup and am looking to
add a MySQL "health" check that can take a node out of the cluster if its
slave is unhealthy, e.g. out of sync. The master/slave master/slave config
is working fine, hence writes in either node are replicated to the other
n
