[Pacemaker] Resource starts on wrong node ?
Hans Lammerts
j.lammerts at chello.nl
Wed Sep 21 10:02:24 UTC 2011
Hi all,
Just started to configure a two node cluster (Centos 6) with drbd 8.4.0-31.el6,
corosync 1.2.3 and pacemaker 1.1.2.
I created three DRBD filesystems, and started to add them in the crm config one by one.
Everything went OK. After adding these resources they start on node1, and when I set node1
in standby, these three DRBD resources failover nicely to the second node. And vice versa.
So far so good.
Next, I added one extra resource, that is supposed to put an IP alias on eth0.
This also works, but strangely enough the alias is set on eth0 of the second node, where I would have
expected it to start on the first node (just as the three drbd resources did).
Why the.... does Pacemaker decide that this resource is to be started on the second node ? I cannot grasp
the reason why.
Hope anyone can tell me what I'm doing wrong.
Thanks,
Hans
Just to be sure, I'll show my config below:
node cl1 \
attributes standby="off"
node cl2 \
attributes standby="off"
primitive drbd0 ocf:linbit:drbd \
params drbd_resource="mysql" drbdconf="/etc/drbd.conf" \
op start interval="0" timeout="240s" \
op monitor interval="20s" timeout="20s" \
op stop interval="0" timeout="100s"
primitive drbd1 ocf:linbit:drbd \
params drbd_resource="www" drbdconf="/etc/drbd.conf" \
op start interval="0" timeout="240s" \
op monitor interval="20s" timeout="20s" \
op stop interval="0" timeout="100s"
primitive drbd2 ocf:linbit:drbd \
params drbd_resource="zarafa" drbdconf="/etc/drbd.conf" \
op start interval="0" timeout="240s" \
op monitor interval="20s" timeout="20s" \
op stop interval="0" timeout="100s"
primitive mysqlfs ocf:heartbeat:Filesystem \
params device="/dev/drbd0" fstype="ext4" directory="/var/lib/mysql" \
op start interval="0" timeout="60s" \
op monitor interval="20s" timeout="40s" \
op stop interval="0" timeout="60s" \
meta target-role="Started"
primitive mysqlip ocf:heartbeat:IPaddr2 \
params ip="192.168.2.30" nic="eth0" cidr_netmask="24" \
op start interval="0s" timeout="60s" \
op monitor interval="5s" timeout="20s" \
op stop interval="0s" timeout="60s" \
meta target-role="Started"
primitive wwwfs ocf:heartbeat:Filesystem \
params device="/dev/drbd1" fstype="ext4" directory="/var/www" \
op start interval="0" timeout="60s" \
op monitor interval="20s" timeout="40s" \
op stop interval="0" timeout="60s"
primitive zarafafs ocf:heartbeat:Filesystem \
params device="/dev/drbd2" fstype="ext4" directory="/var/lib/zarafa" \
op start interval="0" timeout="60s" \
op monitor interval="20s" timeout="40s" \
op stop interval="0" timeout="60s"
ms ms_drbd0 drbd0 \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" target-role="Started"
ms ms_drbd1 drbd1 \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
ms ms_drbd2 drbd2 \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
colocation fs2_on_drbd inf: wwwfs ms_drbd1:Master
colocation fs3_on_drbd inf: zarafafs ms_drbd2:Master
colocation fs_on_drbd inf: mysqlfs ms_drbd0:Master
order fs2_after_drbd inf: ms_drbd1:promote wwwfs:start
order fs3_after_drbd inf: ms_drbd2:promote zarafafs:start
order fs_after_drbd inf: ms_drbd0:promote mysqlfs:start
property $id="cib-bootstrap-options" \
dc-version="1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
no-quorum-policy="ignore" \
stonith-enabled="false"
rsc_defaults $id="rsc-options" \
resource_stickyness="INFINITY" \
migration-threshold="1"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110921/50d3d69e/attachment-0003.html>
More information about the Pacemaker
mailing list