Hello,
I am contacting you because I have a problem with my cluster and I cannot find (nor understand) any information that can help me.

I have a 2 nodes cluster (pacemaker, corosync, pcs) installed on CentOS 7 with a set of configuration.
Everything seems to works fine, but here is what happens:

 * Node1 and Node2 are running well with Node1 as primary
 * I reboot Node2 wich is passive (no changes on Node1)
 * Node2 comes back in the cluster as passive
 * corosync logs shows resources getting started then stopped on Node2
 * "crm_mon" command shows some ressources on Node1 getting restarted

I don't understand how it should work.
If a node comes back, and becomes passive (since Node1 is running primary), there is no reason for the resources to be started then stopped on the new passive node ?

One of my resources becomes unstable because it gets started and then stoped too quickly on Node2, wich seems to make it restart on Node1 without a failover.

I tried several things and solution proposed by different sites and forums but without success.


Is there a way so that the node, which joins the cluster as passive, does not start its own resources ?


thanks in advance


Here are some information just in case :

$ rpm -qa | grep -E "corosync|pacemaker|pcs"
corosync-2.4.5-4.el7.x86_64
pacemaker-cli-1.1.21-4.el7.x86_64
pacemaker-1.1.21-4.el7.x86_64
pcs-0.9.168-4.el7.centos.x86_64
corosynclib-2.4.5-4.el7.x86_64
pacemaker-libs-1.1.21-4.el7.x86_64
pacemaker-cluster-libs-1.1.21-4.el7.x86_64


        <nvpair id="cib-bootstrap-options-stonith-enabled" name="stonith-enabled" 
value="false"/>
        <nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy" 
value="ignore"/>
        <nvpair id="cib-bootstrap-options-dc-deadtime" name="dc-deadtime" 
value="120s"/>
        <nvpair id="cib-bootstrap-options-have-watchdog" name="have-watchdog" 
value="false"/>
        <nvpair id="cib-bootstrap-options-dc-version" name="dc-version" 
value="1.1.21-4.el7-f14e36fd43"/>
        <nvpair id="cib-bootstrap-options-cluster-infrastructure" 
name="cluster-infrastructure" value="corosync"/>
        <nvpair id="cib-bootstrap-options-cluster-name" name="cluster-name" 
value="CLUSTER"/>
        <nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" 
value="1598446314"/>
        <nvpair id="cib-bootstrap-options-default-resource-stickiness" 
name="default-resource-stickiness" value="0"/>




_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to