Hello! Does ping resource and stickiness may work together?
For example I have next resources: primitive P_INTRANET ocf:pacemaker:ping \ params host_list="192.168.56.1 192.168.56.100" multiplier="111" name="ping_intranet" \ op monitor interval="5s" timeout="20s" clone CL_INTRANET P_INTRANET \ meta target-role="Started" globally-unique="false" location L_DRBD_MASTER_01 msDRBD \ rule $id="L_DRBD_MASTER_01-rule" 100: #uname eq first.local location L_DRBD_MASTER_02 msDRBD \ rule $id="L_DRBD_MASTER_02-rule" 10: #uname eq second.local location L_DRBD_MASTER_PING msDRBD \ rule $id="L_DRBD_MASTER_03-rule" ping_intranet: defined ping_intranet rsc_defaults $id="rsc-options" \ resource-stickiness="10000" So when master node doesn't ping ip address -- resource moves to other node. But when ip will up -- resource moves back (cause it location rate: 100+111+111 > 10+111+111) How can I prevent this behavior? Tnx. -- Viacheslav Sov1et Biriukov BR
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
