[Pacemaker] Stopping heartbeat service on one node lead to restart of resources on other node in cluster

[neha chatrath]

Hello,
I have a 2 node cluster with following configuration:
**node $id="9e53a111-0dca-496c-9461-a38f3eec4d0e" mcg2 \
       attributes standby="off"
node $id="a90981f8-d993-4411-89f4-aff7156136d2" mcg1 \
       attributes standby="off"
primitive ClusterIP ocf:mcg:MCG_VIPaddr_RA \
       params ip="192.168.115.50" cidr_netmask="255.255.255.0"
nic="bond1.115:1" \
       op monitor interval="40" timeout="20" \
       meta target-role="Started"
primitive EMS ocf:heartbeat:jboss \
       params jboss_home="/opt/jboss-5.1.0.GA"
java_home="/opt/jdk1.6.0_29/" \
       op start interval="0" timeout="240" \
       op stop interval="0" timeout="240" \
       op monitor interval="30s" timeout="40s"
primitive NDB_MGMT ocf:mcg:NDB_MGM_RA \
       op monitor interval="120" timeout="120"
primitive NDB_VIP ocf:heartbeat:IPaddr2 \
       params ip="192.168.117.50" cidr_netmask="255.255.255.255"
nic="bond0.117:1" \*
      * op monitor interval="30" timeout="10"
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 mysql ocf:mcg:MYSQLD_RA \
       op monitor interval="180" timeout="200"
primitive ndbd ocf:mcg:NDBD_RA \
       op monitor interval="120" timeout="120"
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" interleave="true" notify="true"
ms ms_Tmgr Tmgr \
       meta master-max="1" master-max-node="1" clone-max="2"
clone-node-max="1" interleave="true" notify="true"
ms ms_pimd pimd \
       meta master-max="1" master-max-node="1" clone-max="2"
clone-node-max="1" interleave="true" notify="true"
clone EMS_CLONE EMS \
       meta globally-unique="false" clone-max="2" clone-node-max="1"
target-role="Started"
clone mysqld_clone mysql \
       meta globally-unique="false" clone-max="2" clone-node-max="1"
clone ndbdclone ndbd \
       meta globally-unique="false" clone-max="2" clone-node-max="1"
target-role="Started"
colocation ip_with_Pimd inf: ClusterIP ms_pimd:Master
colocation ip_with_RM inf: ClusterIP ms_Rmgr:Master
colocation ip_with_TM inf: ClusterIP ms_Tmgr:Master
colocation ndb_vip-with-ndb_mgm inf: NDB_MGMT NDB_VIP
order RM-after-mysqld inf: mysqld_clone ms_Rmgr
order TM-after-RM inf: ms_Rmgr ms_Tmgr
order ip-after-pimd inf: ms_pimd ClusterIP
order mysqld-after-ndbd inf: ndbdclone mysqld_clone
order pimd-after-TM inf: ms_Tmgr ms_pimd
property $id="cib-bootstrap-options" \
       dc-version="1.0.11-55a5f5be61c367cbd676c2f0ec4f1c62b38223d7" \
       cluster-infrastructure="Heartbeat" \
       no-quorum-policy="ignore" \
       stonith-enabled="false"
rsc_defaults $id="rsc-options" \
       migration_threshold="3" \
       resource-stickiness="100"*

*With both nodes up and running, if heartbeat service is stopped on any of
the nodes, following resources are restarted on the other node:
mysqld_clone, ms_Rmgr, ms_Tmgr, ms_pimd, ClusterIP