[Pacemaker] How can I restart a clone resource on a specific node ?

[Andrew Beekhof]

On Tue, Nov 9, 2010 at 5:56 PM, oaidel <oaidel at cc.in2p3.fr> wrote:
> Hello,
>
> I have a cluster 2 nodes (RL 5.2) using pacemaker (1.0.9) with corosync
>
> <configuration>
> <crm_config>
> <cluster_property_set id="cib-bootstrap-options">
> <nvpair id="cib-bootstrap-options-dc-version" name="dc-version"
> value="1.0.9-89bd754939df5150de7cd76835f98fe90851b677"/>
> <nvpair id="cib-bootstrap-options-cluster-infrastructure"
> name="cluster-infrastructure" value="openais"/>
> <nvpair id="cib-bootstrap-options-expected-quorum-votes"
> name="expected-quorum-votes" value="2"/>
> <nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy"
> value="ignore"/>
> <nvpair id="cib-bootstrap-options-stonith-enabled" name="stonith-enabled"
> value="false"/>
> <nvpair id="cib-bootstrap-options-symmetric-cluster"
> name="symmetric-cluster" value="true"/>
> <nvpair name="last-lrm-refresh" id="cib-bootstrap-options-last-lrm-refresh"
> value="1289317724"/>
> </cluster_property_set>
> </crm_config>
> <nodes>
> <node type="normal" uname="ccdb11" id="ccdb11">
> <instance_attributes id="nodes-ccdb11">
> <nvpair name="standby" id="nodes-ccdb11-standby" value="off"/>
> </instance_attributes>
> </node>
> <node uname="ccdb12" type="normal" id="ccdb12">
> <instance_attributes id="nodes-ccdb12">
> <nvpair name="standby" id="nodes-ccdb12-standby" value="off"/>
> </instance_attributes>
> </node>
> </nodes>
> <resources>
> <clone id="ocfs2cloneset">
> <meta_attributes id="ocfs2-options">
> <nvpair id="ocfs2-unique" name="globally_unique" value="false"/>
> <nvpair id="ocfs2-notify" name="notify" value="true"/>
> <nvpair id="ocfs2-interleave" name="interleave" value="true"/>
> <nvpair id="ocfs2-options-target-role" name="target-role" value="Started"/>
> </meta_attributes>
> <instance_attributes id="ocfs2cloneset_instance_attributes">
> <nvpair id="ocfs2cloneset-01" name="clone_node_max" value="1"/>
> <nvpair id="ocfs2cloneset-02" name="target_role" value="started"/>
> </instance_attributes>
> <primitive class="ocf" id="ocfs2clone" provider="heartbeat"
> type="Filesystem">
> <operations>
> <op id="ocfs2clone-monitor-10s" interval="10s" name="monitor"
> requires="nothing" timeout="10s"/>
> </operations>
> <instance_attributes id="ocfs2clone_instance_attributes">
> <nvpair id="ocfs2clone-01" name="device"
> value="/dev/mapper/se35106288978Bp1"/>
> <nvpair id="ocfs2clone-02" name="directory" value="/ocfs2"/>
> <nvpair id="ocfs2clone-03" name="fstype" value="ocfs2"/>
> </instance_attributes>
> </primitive>
> </clone>
> <primitive class="lsb" id="mysql" type="mysql">
> <operations>
> <op id="mysql-monitor-120s" interval="120s" name="monitor" timeout="60s"/>
> </operations>
> <meta_attributes id="mysql-meta_attributes">
> <nvpair id="mysql-meta_attributes-target-role" name="target-role"
> value="Started"/>
> </meta_attributes>
> </primitive>
> <primitive class="ocf" id="vip" provider="heartbeat" type="IPaddr2">
> <instance_attributes id="vip-instance_attributes">
> <nvpair id="vip-instance_attributes-ip" name="ip" value="134.158.107.215"/>
> <nvpair id="vip-instance_attributes-cidr_netmask" name="cidr_netmask"
> value="29"/>
> </instance_attributes>
> <operations>
> <op id="vip-monitor" interval="60s" name="monitor"/>
> </operations>
> </primitive>
> <primitive class="ocf" id="Monitor-Cluster" provider="pacemaker"
> type="ClusterMon">
> <instance_attributes id="Monitor-Cluster-instance_attributes">
> <nvpair id="Monitor-Cluster-instance_attributes-htmlfile" name="htmlfile"
> value="/tmp/cluster-monitor.html"/>
> </instance_attributes>
> <instance_attributes id="Monitor-Cluster-instance_attributes-0">
> <nvpair id="Monitor-Cluster-instance_attributes-0-pidfile" name="pidfile"
> value="/tmp/cluster-monitor.pid"/>
> </instance_attributes>
> <instance_attributes id="Monitor-Cluster-instance_attributes-1">
> <nvpair id="Monitor-Cluster-instance_attributes-1-extra_options"
> name="extra_options" value="--mail-to=dba at cc.in2p3.fr"/>
> </instance_attributes>
> <operations>
> <op id="Monitor-Cluster-monitor-10" interval="10" name="monitor"
> timeout="20"/>
> </operations>
> </primitive>
> </resources>
> <constraints>
> <rsc_order id="order-1">
> <resource_set id="ordered-set-0" sequential="true">
> <resource_ref id="ocfs2cloneset"/>
> <resource_ref id="mysql"/>
> <resource_ref id="vip"/>
> </resource_set>
> </rsc_order>
> <rsc_colocation id="coloc-1" score="500">
> <resource_set id="collocated-set-example" sequential="true">
> <resource_ref id="ocfs2cloneset"/>
> <resource_ref id="mysql"/>
> <resource_ref id="vip"/>
> </resource_set>
> </rsc_colocation>
> </constraints>
> <rsc_defaults>
> <meta_attributes id="rsc_defaults-options">
> <nvpair id="rsc_defaults-options-migration-threshold"
> name="migration-threshold" value="1"/>
> <nvpair id="rsc_defaults-options-resource-stickiness"
> name="resource-stickiness" value="100"/>
> </meta_attributes>
> </rsc_defaults>
> <op_defaults>
> <meta_attributes id="op_defaults-options">
> <nvpair id="op_defaults-options-timeout" name="timeout" value="30"/>
> </meta_attributes>
> </op_defaults>
> </configuration>
>
>
> I use ocfs2 as a clone resource on both nodes and my concern is about my
> clone resource "ocfs2cloneset"
> I put one node in standby and when I put it back online Pacemaker has not
> been able to restart ocfsclone on this node.
>
> ccdb11$ crm node standby ccdb11
> ccdb11$ crm node online ccdb11
> ccdb11$crm status
>  Clone Set: ocfs2cloneset
>     Started: [ ccdb12 ]
>     Stopped: [ ocfs2clone:0 ]
>  mysql  (lsb:mysql):    Started ccdb12
>  vip    (ocf::heartbeat:IPaddr2):       Started ccdb12
>  Monitor-Cluster        (ocf::pacemaker:ClusterMon):    Started ccdb12
>
> Since, I have not succeeded to restart ocfs2cloneset on ccdb11 node .
> How can I restart a clone resource on a specific node ?
> I tried to restart/cleanup  the whole ocfs2clone resource but that does not
> work.

Possibly there is something wrong with the RA, but there's nowhere
near enough info to tell.

>
> When I run crm_verify I see the following errors :
>
> crm_verify[13806]: 2010/11/09_17:32:36 ERROR:
> create_notification_boundaries: Creating boundaries for ocfs2cloneset
> crm_verify[13806]: 2010/11/09_17:32:36 ERROR:
> create_notification_boundaries: Creating boundaries for ocfs2cloneset
>
> I have not found any information about these errors.

They're debugging that didn't get removed before I committed :-(
They can be ignored.

> I attached a part of my /var/log/message which displays some details not
> understable for me.
>
>
> Any help will be very appreciated.
>
> Regards,
> Osman
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>