Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Pacemaker

don't want to restart clone resource

 

 

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded


shafanghao at gmail

Dec 1, 2011, 12:03 AM

Post #1 of 17 (2675 views)
Permalink
don't want to restart clone resource

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
Attachments: messages.log (16.2 KB)


andrew at beekhof

Dec 8, 2011, 1:23 PM

Post #2 of 17 (2601 views)
Permalink
Re: don't want to restart clone resource [In reply to]

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)

2011/12/1 Sha Fanghao <shafanghao [at] gmail>:
> 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
> 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
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 at linbit

Dec 16, 2011, 10:42 AM

Post #3 of 17 (2577 views)
Permalink
Re: don't want to restart clone resource [In reply to]

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>:
> > 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
> > 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
> 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.

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


shafanghao at gmail

Dec 17, 2011, 1:50 AM

Post #4 of 17 (2568 views)
Permalink
Re: don't want to restart clone resource [In reply to]

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)



Anything else except "messages" file?





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?



Exactly.

I have tried to set "stop-orphan-resources" and "stop-orphan-actions" options to FALSE,

it couldn't be resolved.



>

> 2011/12/1 Sha Fanghao <shafanghao [at] gmail>:

> > 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

> > 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

> 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.



_______________________________________________

Pacemaker mailing list: Pacemaker [at] oss

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
Attachments: messages (16.2 KB)


shafanghao at gmail

Feb 1, 2012, 1:39 AM

Post #5 of 17 (2490 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hi Lars,

Yes, you are right. But how to prevent the "orphaned" resources from
stopping by default, please?

2011/12/17 Lars Ellenberg <lars.ellenberg [at] linbit>

> 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>:
> > > 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
> > > 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
> > 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.
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>


andreas at hastexo

Feb 1, 2012, 6:43 AM

Post #6 of 17 (2491 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hello,

On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> Hi Lars,
>
> Yes, you are right. But how to prevent the "orphaned" resources from
> stopping by default, please?

crm configure property stop-orphan-resources=false

Regards,
Andreas

--
Need help with Pacemaker?
http://www.hastexo.com/now


>
> 2011/12/17 Lars Ellenberg <lars.ellenberg [at] linbit
> <mailto:lars.ellenberg [at] linbit>>
>
> 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
> <mailto:shafanghao [at] gmail>>:
> > > 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
> <mailto:Pacemaker [at] oss>
> > > 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
> <mailto:Pacemaker [at] oss>
> > 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.
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> <mailto:Pacemaker [at] oss>
> 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
> 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
Attachments: signature.asc (0.22 KB)


lars.ellenberg at linbit

Feb 1, 2012, 9:57 AM

Post #7 of 17 (2485 views)
Permalink
Re: don't want to restart clone resource [In reply to]

On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> Hello,
>
> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> > Hi Lars,
> >
> > Yes, you are right. But how to prevent the "orphaned" resources from
> > stopping by default, please?
>
> crm configure property stop-orphan-resources=false

Well, sure. But for "normal" ophans,
you actually want them to be stopped.

No, pacemaker needs some additional smarts to recognize
that there actually are no orphans, maybe by first relabling,
and only then checking for instance label > clone-max.

Did you file a bugzilla?
Has that made progress?


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

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


bubble at hoster-ok

Feb 1, 2012, 12:15 PM

Post #8 of 17 (2494 views)
Permalink
Re: don't want to restart clone resource [In reply to]

01.02.2012 20:57, Lars Ellenberg wrote:
> On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>> Hello,
>>
>> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>>> Hi Lars,
>>>
>>> Yes, you are right. But how to prevent the "orphaned" resources from
>>> stopping by default, please?
>>
>> crm configure property stop-orphan-resources=false
>
> Well, sure. But for "normal" ophans,
> you actually want them to be stopped.
>
> No, pacemaker needs some additional smarts to recognize
> that there actually are no orphans, maybe by first relabling,
> and only then checking for instance label > clone-max.

I use clone-max=<max-number-of-cluster-nodes> for important clones, so
they never become orphaned.

Best,
Vladislav

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


andrew at beekhof

Feb 2, 2012, 2:02 AM

Post #9 of 17 (2477 views)
Permalink
Re: don't want to restart clone resource [In reply to]

On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
<lars.ellenberg [at] linbit> wrote:
> On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>> Hello,
>>
>> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>> > Hi Lars,
>> >
>> > Yes, you are right. But how to prevent the "orphaned" resources from
>> > stopping by default, please?
>>
>> crm configure property stop-orphan-resources=false
>
> Well, sure. But for "normal" ophans,
> you actually want them to be stopped.
>
> No, pacemaker needs some additional smarts to recognize
> that there actually are no orphans, maybe by first relabling,
> and only then checking for instance label > clone-max.

Instance label doesn't come into the equation.
It might look like it does on the outside, but its more complicated than that.

>
> Did you file a bugzilla?
> Has that made progress?
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
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


shafanghao at gmail

Feb 3, 2012, 2:35 AM

Post #10 of 17 (2465 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Sorry, I don't know how to file a bug, and i have only "messages" file.

I have tried to set clone-max=3, and after removing node-1, the clone
resource running on node-2 has not restart.
But when I add another node-3 to cluster with "hb_addnode", the clone
resource running on node-2 became orphaned and restart.

As attached "messages" file,
I couldn't understand this line:
"find_clone: Internally renamed node-app-rsc:2 on node-2 to node-app-rsc:3
(ORPHAN)".

2012/2/2 Andrew Beekhof <andrew [at] beekhof>

> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
> <lars.ellenberg [at] linbit> wrote:
> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> >> Hello,
> >>
> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> >> > Hi Lars,
> >> >
> >> > Yes, you are right. But how to prevent the "orphaned" resources from
> >> > stopping by default, please?
> >>
> >> crm configure property stop-orphan-resources=false
> >
> > Well, sure. But for "normal" ophans,
> > you actually want them to be stopped.
> >
> > No, pacemaker needs some additional smarts to recognize
> > that there actually are no orphans, maybe by first relabling,
> > and only then checking for instance label > clone-max.
>
> Instance label doesn't come into the equation.
> It might look like it does on the outside, but its more complicated than
> that.
>
> >
> > Did you file a bugzilla?
> > Has that made progress?
> >
> >
> > --
> > : Lars Ellenberg
> > : LINBIT | Your Way to High Availability
> > : DRBD/HA support and consulting http://www.linbit.com
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker [at] oss
> > 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
> 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
>


shafanghao at gmail

Feb 3, 2012, 2:39 AM

Post #11 of 17 (2464 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Sorry, I don't know how to file a bug, and i have only "messages" file.

I have tried to set clone-max=3, and after removing node-1, the clone resource
running on node-2 has not restart.
But when I add another node-3 to cluster with "hb_addnode", the clone resource
running on node-2 became orphaned and restart.

As attached "messages" file,
I couldn't understand this line:
"find_clone: Internally renamed node-app-rsc:2 on node-2 to node-app-rsc:3
(ORPHAN)".

2012/2/2 Andrew Beekhof <andrew [at] beekhof>

> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
> <lars.ellenberg [at] linbit> wrote:
> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> >> Hello,
> >>
> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> >> > Hi Lars,
> >> >
> >> > Yes, you are right. But how to prevent the "orphaned" resources from
> >> > stopping by default, please?
> >>
> >> crm configure property stop-orphan-resources=false
> >
> > Well, sure. But for "normal" ophans,
> > you actually want them to be stopped.
> >
> > No, pacemaker needs some additional smarts to recognize
> > that there actually are no orphans, maybe by first relabling,
> > and only then checking for instance label > clone-max.
>
> Instance label doesn't come into the equation.
> It might look like it does on the outside, but its more complicated than
> that.
>
> >
> > Did you file a bugzilla?
> > Has that made progress?
> >
> >
> > --
> > : Lars Ellenberg
> > : LINBIT | Your Way to High Availability
> > : DRBD/HA support and consulting http://www.linbit.com
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker [at] oss
> > 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
> 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
>
Attachments: messages (79.8 KB)


andrew at beekhof

Feb 3, 2012, 2:15 PM

Post #12 of 17 (2493 views)
Permalink
Re: don't want to restart clone resource [In reply to]

On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
> Sorry, I don't know how to file a bug,

See the links at the bottom of every mail on this list?

> and i have only "messages" file.

man crm_report

>
> I have tried to set clone-max=3, and after removing node-1, the clone
> resource running on node-2 has not restart.
> But when I add another node-3 to cluster with "hb_addnode", the clone
> resource running on node-2 became orphaned and restart.
>
> As attached "messages" file,
> I couldn't understand this line:
> "find_clone: Internally renamed node-app-rsc:2 on node-2 to node-app-rsc:3
> (ORPHAN)".
>
> 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
>>
>> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
>> <lars.ellenberg [at] linbit> wrote:
>> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>> >> Hello,
>> >>
>> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>> >> > Hi Lars,
>> >> >
>> >> > Yes, you are right. But how to prevent the "orphaned" resources from
>> >> > stopping by default, please?
>> >>
>> >> crm configure property stop-orphan-resources=false
>> >
>> > Well, sure. But for "normal" ophans,
>> > you actually want them to be stopped.
>> >
>> > No, pacemaker needs some additional smarts to recognize
>> > that there actually are no orphans, maybe by first relabling,
>> > and only then checking for instance label > clone-max.
>>
>> Instance label doesn't come into the equation.
>> It might look like it does on the outside, but its more complicated than
>> that.
>>
>> >
>> > Did you file a bugzilla?
>> > Has that made progress?
>> >
>> >
>> > --
>> > : Lars Ellenberg
>> > : LINBIT | Your Way to High Availability
>> > : DRBD/HA support and consulting http://www.linbit.com
>> >
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker [at] oss
>> > 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
>> 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
> 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
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


shafanghao at gmail

Feb 7, 2012, 10:48 PM

Post #13 of 17 (2433 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hi Andrew,
Is crm_report included in pacemaker-1.0.12-1.el5.centos?
I couldn't find it.

2012/2/4 Andrew Beekhof <andrew [at] beekhof>

> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
> > Sorry, I don't know how to file a bug,
>
> See the links at the bottom of every mail on this list?
>
> > and i have only "messages" file.
>
> man crm_report
>
> >
> > I have tried to set clone-max=3, and after removing node-1, the clone
> > resource running on node-2 has not restart.
> > But when I add another node-3 to cluster with "hb_addnode", the clone
> > resource running on node-2 became orphaned and restart.
> >
> > As attached "messages" file,
> > I couldn't understand this line:
> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
> node-app-rsc:3
> > (ORPHAN)".
> >
> > 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
> >>
> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
> >> <lars.ellenberg [at] linbit> wrote:
> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> >> >> Hello,
> >> >>
> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> >> >> > Hi Lars,
> >> >> >
> >> >> > Yes, you are right. But how to prevent the "orphaned" resources
> from
> >> >> > stopping by default, please?
> >> >>
> >> >> crm configure property stop-orphan-resources=false
> >> >
> >> > Well, sure. But for "normal" ophans,
> >> > you actually want them to be stopped.
> >> >
> >> > No, pacemaker needs some additional smarts to recognize
> >> > that there actually are no orphans, maybe by first relabling,
> >> > and only then checking for instance label > clone-max.
> >>
> >> Instance label doesn't come into the equation.
> >> It might look like it does on the outside, but its more complicated than
> >> that.
> >>
> >> >
> >> > Did you file a bugzilla?
> >> > Has that made progress?
> >> >
> >> >
> >> > --
> >> > : Lars Ellenberg
> >> > : LINBIT | Your Way to High Availability
> >> > : DRBD/HA support and consulting http://www.linbit.com
> >> >
> >> > _______________________________________________
> >> > Pacemaker mailing list: Pacemaker [at] oss
> >> > 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
> >> 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
> > 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
> 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
>


andrew at beekhof

Feb 12, 2012, 5:17 PM

Post #14 of 17 (2410 views)
Permalink
Re: don't want to restart clone resource [In reply to]

On Wed, Feb 8, 2012 at 5:48 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
> Hi Andrew,
> Is crm_report included in pacemaker-1.0.12-1.el5.centos?
> I couldn't find it.

/headslap

I added it to the source but neglected to actually install it.

hb_report should be available though

>
>
> 2012/2/4 Andrew Beekhof <andrew [at] beekhof>
>>
>> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
>> > Sorry, I don't know how to file a bug,
>>
>> See the links at the bottom of every mail on this list?
>>
>> > and i have only "messages" file.
>>
>> man crm_report
>>
>> >
>> > I have tried to set clone-max=3, and after removing node-1, the clone
>> > resource running on node-2 has not restart.
>> > But when I add another node-3 to cluster with "hb_addnode", the clone
>> > resource running on node-2 became orphaned and restart.
>> >
>> > As attached "messages" file,
>> > I couldn't understand this line:
>> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
>> > node-app-rsc:3
>> > (ORPHAN)".
>> >
>> > 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
>> >>
>> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
>> >> <lars.ellenberg [at] linbit> wrote:
>> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>> >> >> Hello,
>> >> >>
>> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>> >> >> > Hi Lars,
>> >> >> >
>> >> >> > Yes, you are right. But how to prevent the "orphaned" resources
>> >> >> > from
>> >> >> > stopping by default, please?
>> >> >>
>> >> >> crm configure property stop-orphan-resources=false
>> >> >
>> >> > Well, sure. But for "normal" ophans,
>> >> > you actually want them to be stopped.
>> >> >
>> >> > No, pacemaker needs some additional smarts to recognize
>> >> > that there actually are no orphans, maybe by first relabling,
>> >> > and only then checking for instance label > clone-max.
>> >>
>> >> Instance label doesn't come into the equation.
>> >> It might look like it does on the outside, but its more complicated
>> >> than
>> >> that.
>> >>
>> >> >
>> >> > Did you file a bugzilla?
>> >> > Has that made progress?
>> >> >
>> >> >
>> >> > --
>> >> > : Lars Ellenberg
>> >> > : LINBIT | Your Way to High Availability
>> >> > : DRBD/HA support and consulting http://www.linbit.com
>> >> >
>> >> > _______________________________________________
>> >> > Pacemaker mailing list: Pacemaker [at] oss
>> >> > 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
>> >> 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
>> > 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
>> 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
> 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
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


shafanghao at gmail

Feb 22, 2012, 5:54 PM

Post #15 of 17 (2370 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hi Andrew,
Hi Lars,
I have reported it in bugzilla.
http://bugs.clusterlabs.org/show_bug.cgi?id=5038


2012/2/13 Andrew Beekhof <andrew [at] beekhof>

> On Wed, Feb 8, 2012 at 5:48 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
> > Hi Andrew,
> > Is crm_report included in pacemaker-1.0.12-1.el5.centos?
> > I couldn't find it.
>
> /headslap
>
> I added it to the source but neglected to actually install it.
>
> hb_report should be available though
>
> >
> >
> > 2012/2/4 Andrew Beekhof <andrew [at] beekhof>
> >>
> >> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail>
> wrote:
> >> > Sorry, I don't know how to file a bug,
> >>
> >> See the links at the bottom of every mail on this list?
> >>
> >> > and i have only "messages" file.
> >>
> >> man crm_report
> >>
> >> >
> >> > I have tried to set clone-max=3, and after removing node-1, the clone
> >> > resource running on node-2 has not restart.
> >> > But when I add another node-3 to cluster with "hb_addnode", the clone
> >> > resource running on node-2 became orphaned and restart.
> >> >
> >> > As attached "messages" file,
> >> > I couldn't understand this line:
> >> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
> >> > node-app-rsc:3
> >> > (ORPHAN)".
> >> >
> >> > 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
> >> >>
> >> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
> >> >> <lars.ellenberg [at] linbit> wrote:
> >> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> >> >> >> Hello,
> >> >> >>
> >> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> >> >> >> > Hi Lars,
> >> >> >> >
> >> >> >> > Yes, you are right. But how to prevent the "orphaned" resources
> >> >> >> > from
> >> >> >> > stopping by default, please?
> >> >> >>
> >> >> >> crm configure property stop-orphan-resources=false
> >> >> >
> >> >> > Well, sure. But for "normal" ophans,
> >> >> > you actually want them to be stopped.
> >> >> >
> >> >> > No, pacemaker needs some additional smarts to recognize
> >> >> > that there actually are no orphans, maybe by first relabling,
> >> >> > and only then checking for instance label > clone-max.
> >> >>
> >> >> Instance label doesn't come into the equation.
> >> >> It might look like it does on the outside, but its more complicated
> >> >> than
> >> >> that.
> >> >>
> >> >> >
> >> >> > Did you file a bugzilla?
> >> >> > Has that made progress?
> >> >> >
> >> >> >
> >> >> > --
> >> >> > : Lars Ellenberg
> >> >> > : LINBIT | Your Way to High Availability
> >> >> > : DRBD/HA support and consulting http://www.linbit.com
> >> >> >
> >> >> > _______________________________________________
> >> >> > Pacemaker mailing list: Pacemaker [at] oss
> >> >> > 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
> >> >> 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
> >> > 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
> >> 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
> > 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
> 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
>


shafanghao at gmail

Mar 28, 2012, 1:01 AM

Post #16 of 17 (2316 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hi Andrew,
After your patch, I encountered a new problem,
and I have reported it in bugzilla.
http://bugs.clusterlabs.org/show_bug.cgi?id=5038

2012/2/23 Fanghao Sha <shafanghao [at] gmail>

> Hi Andrew,
> Hi Lars,
> I have reported it in bugzilla.
> http://bugs.clusterlabs.org/show_bug.cgi?id=5038
>
>
> 2012/2/13 Andrew Beekhof <andrew [at] beekhof>
>
>> On Wed, Feb 8, 2012 at 5:48 PM, Fanghao Sha <shafanghao [at] gmail> wrote:
>> > Hi Andrew,
>> > Is crm_report included in pacemaker-1.0.12-1.el5.centos?
>> > I couldn't find it.
>>
>> /headslap
>>
>> I added it to the source but neglected to actually install it.
>>
>> hb_report should be available though
>>
>> >
>> >
>> > 2012/2/4 Andrew Beekhof <andrew [at] beekhof>
>> >>
>> >> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail>
>> wrote:
>> >> > Sorry, I don't know how to file a bug,
>> >>
>> >> See the links at the bottom of every mail on this list?
>> >>
>> >> > and i have only "messages" file.
>> >>
>> >> man crm_report
>> >>
>> >> >
>> >> > I have tried to set clone-max=3, and after removing node-1, the clone
>> >> > resource running on node-2 has not restart.
>> >> > But when I add another node-3 to cluster with "hb_addnode", the clone
>> >> > resource running on node-2 became orphaned and restart.
>> >> >
>> >> > As attached "messages" file,
>> >> > I couldn't understand this line:
>> >> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
>> >> > node-app-rsc:3
>> >> > (ORPHAN)".
>> >> >
>> >> > 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
>> >> >>
>> >> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
>> >> >> <lars.ellenberg [at] linbit> wrote:
>> >> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>> >> >> >> Hello,
>> >> >> >>
>> >> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>> >> >> >> > Hi Lars,
>> >> >> >> >
>> >> >> >> > Yes, you are right. But how to prevent the "orphaned" resources
>> >> >> >> > from
>> >> >> >> > stopping by default, please?
>> >> >> >>
>> >> >> >> crm configure property stop-orphan-resources=false
>> >> >> >
>> >> >> > Well, sure. But for "normal" ophans,
>> >> >> > you actually want them to be stopped.
>> >> >> >
>> >> >> > No, pacemaker needs some additional smarts to recognize
>> >> >> > that there actually are no orphans, maybe by first relabling,
>> >> >> > and only then checking for instance label > clone-max.
>> >> >>
>> >> >> Instance label doesn't come into the equation.
>> >> >> It might look like it does on the outside, but its more complicated
>> >> >> than
>> >> >> that.
>> >> >>
>> >> >> >
>> >> >> > Did you file a bugzilla?
>> >> >> > Has that made progress?
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > : Lars Ellenberg
>> >> >> > : LINBIT | Your Way to High Availability
>> >> >> > : DRBD/HA support and consulting http://www.linbit.com
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > Pacemaker mailing list: Pacemaker [at] oss
>> >> >> > 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
>> >> >> 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
>> >> > 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
>> >> 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
>> > 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
>> 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
>>
>
>


shafanghao at gmail

Mar 30, 2012, 8:49 PM

Post #17 of 17 (2304 views)
Permalink
Re: don't want to restart clone resource [In reply to]

Hi Andrew,
The problem is not resolved, and I have upgraded the bugzilla.
http://bugs.clusterlabs.org/show_bug.cgi?id=5038
Appreciate your reply. :)

2012/3/28 Fanghao Sha <shafanghao [at] gmail>

> Hi Andrew,
> After your patch, I encountered a new problem,
> and I have reported it in bugzilla.
> http://bugs.clusterlabs.org/show_bug.cgi?id=5038
>
>
> 2012/2/23 Fanghao Sha <shafanghao [at] gmail>
>
>> Hi Andrew,
>> Hi Lars,
>> I have reported it in bugzilla.
>> http://bugs.clusterlabs.org/show_bug.cgi?id=5038
>>
>>
>> 2012/2/13 Andrew Beekhof <andrew [at] beekhof>
>>
>>> On Wed, Feb 8, 2012 at 5:48 PM, Fanghao Sha <shafanghao [at] gmail>
>>> wrote:
>>> > Hi Andrew,
>>> > Is crm_report included in pacemaker-1.0.12-1.el5.centos?
>>> > I couldn't find it.
>>>
>>> /headslap
>>>
>>> I added it to the source but neglected to actually install it.
>>>
>>> hb_report should be available though
>>>
>>> >
>>> >
>>> > 2012/2/4 Andrew Beekhof <andrew [at] beekhof>
>>> >>
>>> >> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao [at] gmail>
>>> wrote:
>>> >> > Sorry, I don't know how to file a bug,
>>> >>
>>> >> See the links at the bottom of every mail on this list?
>>> >>
>>> >> > and i have only "messages" file.
>>> >>
>>> >> man crm_report
>>> >>
>>> >> >
>>> >> > I have tried to set clone-max=3, and after removing node-1, the
>>> clone
>>> >> > resource running on node-2 has not restart.
>>> >> > But when I add another node-3 to cluster with "hb_addnode", the
>>> clone
>>> >> > resource running on node-2 became orphaned and restart.
>>> >> >
>>> >> > As attached "messages" file,
>>> >> > I couldn't understand this line:
>>> >> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
>>> >> > node-app-rsc:3
>>> >> > (ORPHAN)".
>>> >> >
>>> >> > 2012/2/2 Andrew Beekhof <andrew [at] beekhof>
>>> >> >>
>>> >> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
>>> >> >> <lars.ellenberg [at] linbit> wrote:
>>> >> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
>>> >> >> >> Hello,
>>> >> >> >>
>>> >> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
>>> >> >> >> > Hi Lars,
>>> >> >> >> >
>>> >> >> >> > Yes, you are right. But how to prevent the "orphaned"
>>> resources
>>> >> >> >> > from
>>> >> >> >> > stopping by default, please?
>>> >> >> >>
>>> >> >> >> crm configure property stop-orphan-resources=false
>>> >> >> >
>>> >> >> > Well, sure. But for "normal" ophans,
>>> >> >> > you actually want them to be stopped.
>>> >> >> >
>>> >> >> > No, pacemaker needs some additional smarts to recognize
>>> >> >> > that there actually are no orphans, maybe by first relabling,
>>> >> >> > and only then checking for instance label > clone-max.
>>> >> >>
>>> >> >> Instance label doesn't come into the equation.
>>> >> >> It might look like it does on the outside, but its more complicated
>>> >> >> than
>>> >> >> that.
>>> >> >>
>>> >> >> >
>>> >> >> > Did you file a bugzilla?
>>> >> >> > Has that made progress?
>>> >> >> >
>>> >> >> >
>>> >> >> > --
>>> >> >> > : Lars Ellenberg
>>> >> >> > : LINBIT | Your Way to High Availability
>>> >> >> > : DRBD/HA support and consulting http://www.linbit.com
>>> >> >> >
>>> >> >> > _______________________________________________
>>> >> >> > Pacemaker mailing list: Pacemaker [at] oss
>>> >> >> > 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
>>> >> >> 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
>>> >> > 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
>>> >> 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
>>> > 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
>>> 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
>>>
>>
>>
>

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.