[Pacemaker] Stopping heartbeat on active node leads to restart of resources on standby node

[neha chatrath]

Hello,
I have a 2 node cluster with following configuration:
*crm configure show
node $id="16738ea4-adae-483f-9d79-b0ecce8050f4" mcg2
primitive ClusterIP ocf:mcg:MCG_VIPaddr_RA \
        params ip="192.168.113.67" cidr_netmask="255.255.255.0"
nic="eth0:1" \
        op monitor interval="40" timeout="20"
primitive Rmgr ocf:mcg:RM_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="restart" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
primitive Tmgr ocf:mcg:TM_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="restart" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
primitive pimd ocf:mcg:PIMD_RA \
        op monitor interval="60" role="Master" timeout="30"
on-fail="restart" \
        op monitor interval="40" role="Slave" timeout="40" on-fail="restart"
ms ms_Rmgr Rmgr \
        meta master-max="1" master-max-node="1" clone-max="2"
clone-node-max="1" notify="true"
ms ms_Tmgr Tmgr \
        meta master-max="1" master-max-node="1" clone-max="2"
clone-node-max="1" notify="true"
ms ms_pimd pimd \
        meta master-max="1" master-max-node="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Stopped"
colocation ip_with_Rmgr inf: ClusterIP ms_Rmgr:Master
colocation ip_with_Tmgr inf: ClusterIP ms_Tmgr:Master
colocation ip_with_pimd inf: ClusterIP ms_pimd:Master
order TM-after-RM inf: ms_Rmgr:promote ms_Tmgr:start
order ip-after-pimd inf: ms_pimd:promote ClusterIP:start
order pimd-after-TM inf: ms_Tmgr:promote ms_pimd:start
property $id="cib-bootstrap-options" \
        dc-version="1.0.11-9af47ddebcad19e35a61b2a20301dc038018e8e8" \
        cluster-infrastructure="Heartbeat" \
        no-quorum-policy="ignore" \
        stonith-enabled="false"
rsc_defaults $id="rsc-options" \
        migration_threshold="3" \
        resource-stickiness="100"
*With both Acitve and Standby nodes up and running, if I stop Heartbeat on
Active node, all the resources on Standby node,  first receives stop and
then start from Pacemaker.
As per the idea behind clustering, all the master/slave resources on
Standby should simply receive Promote.

Can somebody comment on this behavior?

Thanks and regards
Neha Chatrath
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120103/8440ac19/attachment-0002.html>