[Pacemaker] Drbd on a asymmetric cluster

Arthur B. Olsen ABO at ft.fo
Fri Mar 11 06:30:43 EST 2011

My config is:

node sql01 attributes standby="off"
node sql02 attributes standby="off"
primitive drbd_mysql ocf:linbit:drbd params drbd_resource="r0" op monitor interval="15s"
primitive fs_mysql ocf:heartbeat:Filesystem params device="/dev/drbd0" directory="/datastore01" fstype="ext4"
primitive ip_mysql ocf:heartbeat:IPaddr2 params ip=""
primitive mysqld lsb:mysql
group mysql fs_mysql ip_mysql mysqld
ms ms_drbd_mysql drbd_mysql meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
location ms_drbd_mysql_on_both ms_drbd_mysql rule $id="ms_drbd_mysql_on_both-rule" inf: #uname eq sql01 or #uname eq sql02
location mysql_pri_loc mysql inf: sql01
location mysql_alt_loc mysql 100: sql02
colocation mysql_on_drbd inf: mysql ms_drbd_mysql:Master
order mysql_after_drbd inf: ms_drbd_mysql:promote mysql:start
property $id="cib-bootstrap-options" dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" cluster-infrastructure="openais" expected-quorum-votes="2" stonith-enabled="false" symmetric-cluster="false" no-quorum-policy="ignore"

I hope someone can explain this to me. It starts everything up in sql01 as primary and sql02 as secondary. When i put sql01 in standby it moves to sql02.
But when i put sql01 online, the resources stay put on sql02. My stickiness is zero.

I have tried to replace the ms_drbd_mysql_on_both with:
location ms_drbd_mysql_pri_loc ms_drbd_mysql inf: sql01
location ms_drbd_mysql_sec_loc ms_drbd_mysql 100: sql02

Then it freaks out, switching rapidly between

Node sql01: online
drbd_mysql:0 (ocf::linbit:drbd) Slave
Node sql02: online
drbd_mysql:1 (ocf::linbit:drbd) Slave


Node sql01: online
Node sql02: online
drbd_mysql:1 (ocf::linbit:drbd) Slave

I can't find any examples on how to do drbd on an asymmetric cluster

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110311/11730ac5/attachment-0002.html>

More information about the Pacemaker mailing list