[Pacemaker] don't want to restart clone resource

[Lars Ellenberg]

On Fri, Dec 09, 2011 at 08:23:36AM +1100, Andrew Beekhof wrote:
> Can you file a bug and attach a crm_report to it please?
> Unfortunately there's not enough information here to figure out the
> cause (although it does look like a bug)


Node count drops from three to two,
 rsc:2 becomes the label of "orphaned" resources,
 "orphanes" are to be stopped by default?

Something like that?

> 
> 2011/12/1 Sha Fanghao <shafanghao at gmail.com>:
> > Hi,
> >
> >
> >
> > I have a cluster 3 nodes (CentOS 5.2) using pacemaker-1.0.11(also 1.0.12),
> > with heartbeat-3.0.3.
> >
> > You can see the configuration:
> >
> >
> >
> > #crm configure show:
> >
> > node $id="85e0ca02-7aa4-45c8-9911-4035e1e6ee15" node-2
> >
> > node $id="a046bd1e-6267-49e5-902d-c87b6ed1dcb9" node-0
> >
> > node $id="d0f0b2ab-f243-4f78-b541-314fa7d6b346" node-1
> >
> > primitive failover-ip ocf:heartbeat:IPaddr2 \
> >
> >         params ip="10.10.5.83" \
> >
> >         op monitor interval="5s"
> >
> > primitive master-app-rsc lsb:cluster-master \
> >
> >         op monitor interval="5s"
> >
> > primitive node-app-rsc lsb:cluster-node \
> >
> >         op monitor interval="5s"
> >
> > group group-dc failover-ip master-app-rsc
> >
> > clone clone-node-app-rsc node-app-rsc
> >
> > location rule-group-dc group-dc \
> >
> >         rule $id="rule-group-dc-rule" -inf: #is_dc eq false
> >
> > property $id="cib-bootstrap-options" \
> >
> >         start-failure-is-fatal="false" \
> >
> >         no-quorum-policy="ignore" \
> >
> >         symmetric-cluster="true" \
> >
> >         stonith-enabled="false" \
> >
> >         dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \
> >
> >         cluster-infrastructure="Heartbeat"
> >
> >
> >
> > #crm_mon -n -1:
> >
> > ============
> >
> > Last updated: Sat Oct 29 08:44:14 2011
> >
> > Stack: Heartbeat
> >
> > Current DC: node-0 (a046bd1e-6267-49e5-902d-c87b6ed1dcb9) - partition with
> > quorum
> >
> > Version: 1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87
> >
> > 3 Nodes configured, unknown expected votes
> >
> > 2 Resources configured.
> >
> > ============
> >
> >
> >
> > Node node-0 (a046bd1e-6267-49e5-902d-c87b6ed1dcb9): online
> >
> >         master-app-rsc  (lsb:cluster-master) Started
> >
> >         failover-ip     (ocf::heartbeat:IPaddr2) Started
> >
> >         node-app-rsc:0  (lsb:cluster-node) Started
> >
> > Node node-1 (d0f0b2ab-f243-4f78-b541-314fa7d6b346): online
> >
> >         node-app-rsc:1  (lsb:cluster-node) Started
> >
> > Node node-2 (85e0ca02-7aa4-45c8-9911-4035e1e6ee15): online
> >
> >         node-app-rsc:2  (lsb:cluster-node) Started
> >
> >
> >
> >
> >
> > The problem:
> >
> > After stopping heartbeat service on node-1, if I remove node-1 with command
> > "hb_delnode node-1 && crm node delete node-1", then
> >
> > the clone resource(node-app-rsc:2) running on the node-2 will restart and
> > change to "node-app-rsc:1".
> >
> > You know, the node-app-rsc is my application, and I don't want it to
> > restart.
> >
> > How could I do, Please?
> >
> >
> >
> > Any help will be very appreciated. :)
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >          Fanghao Sha
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at 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://bugs.clusterlabs.org
> >
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://bugs.clusterlabs.org

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.