[ClusterLabs] Antw: Pacemaker restart resources when node joins cluster after failback

[Ulrich Windl]

>>> Dharmesh <cutedharmesh at gmail.com> schrieb am 19.05.2016 um 13:18 in Nachricht
<CAGgFXcxOmMuGhVJVHSnRhhaN+ZZkdWCZDQAtKLUsUXmMeHCRdw at mail.gmail.com>:
> Hi,
> 
> i am having a 2 node Debian cluster with resources configured in it.
> Everything is working fine apart from one thing.

Usually you find the reasons in the logs (syslog, cluster log, etc.).

> 
> As and when one of my two node joins the cluster, the resources configured
> on currently active node gets restarted. I am not able to figure out why
> cluster is behaving like this.
> 
> Below is the configuration of my cluster
> 
> node $id="775bad88-0954-40bf-b9e4-4f012a76a34c" testsrv2 \
>         attributes standby="off"
> node $id="b1d07507-6191-425c-bee3-14229c85820f" testsrv1 \
>         attributes standby="off"
> primitive ClusterIp ocf:heartbeat:IPaddr2 \
>         params ip="192.168.120.209" nic="eth0" cidr_netmask="24" \
>         op monitor start-delay="0" interval="30" \
>         meta target-role="started"
> primitive DBClusterIp ocf:heartbeat:IPaddr2 \
>         params ip="192.168.120.210" nic="eth0" cidr_netmask="24" \
>         op monitor interval="30" start-delay="0" \
>         meta target-role="started"
> primitive Postgres-9.3 lsb:postgres-9.3-openscg \
>         op start interval="0" timeout="15" \
>         op stop interval="0" timeout="15" \
>         op monitor interval="15" timeout="15" start-delay="15" \
>         meta target-role="started" migration-threshold="1"
> primitive PowerDns lsb:pdns \
>         op start interval="0" timeout="15" \
>         op stop interval="0" timeout="15" \
>         op monitor interval="15" timeout="15" start-delay="15" \
>         meta target-role="started" migration-threshold="2"
> primitive PsqlMasterToStandby ocf:heartbeat:PsqlMasterToStandby \
>         op start interval="0" timeout="20" start-delay="10" \
>         op monitor interval="10" timeout="240" start-delay="10" \
>         op stop interval="0" timeout="20" \
>         meta target-role="started"
> primitive PsqlPromote ocf:heartbeat:PsqlPromote \
>         op start interval="0" timeout="20" \
>         op stop interval="0" timeout="20" \
>         op monitor interval="10" timeout="20" start-delay="10" \
>         meta target-role="started"
> group Database Postgres-9.3 PsqlPromote
> colocation col_Database_DBClusterIp inf: Database DBClusterIp
> colocation col_Database_PsqlMasterToStandby inf: Database
> PsqlMasterToStandby
> colocation col_PowerDns_ClusterIp inf: PowerDns ClusterIp
> order ord_Database_DBClusterIp inf: Database DBClusterIp
> order ord_Database_PsqlMasterToStandby inf: Database PsqlMasterToStandby
> order ord_PowerDns_ClusterIp inf: PowerDns ClusterIp
> property $id="cib-bootstrap-options" \
>         stonith-enabled="false" \
>         dc-version="1.1.10-42f2063" \
>         cluster-infrastructure="heartbeat" \
>         last-lrm-refresh="1453192778"
> rsc_defaults $id="rsc-options" \
>         resource-stickiness="100" \
>         failure-timeout="60s"
> #vim:set syntax=pcmk
> 
> Let me know if my configuration is not appropriate or some new
> configuration needs to be done.
> 
> Thanks and regards,
> 
> -- 
> Dharmesh Kumar