[ClusterLabs] Resource getting hard-flipped when node recovers

[Andrew Beekhof]

> On 15 May 2015, at 3:24 am, Matthew Vernon <mcv21 at cam.ac.uk> wrote:
> 
> Hi,
> 
> I have a 3-node pacemaker/corosync cluster (output of crm configure save
> below); my resource is a xen guest, and if I make its live node standby,
> then it is live-migrated, as you'd expect.
> 
> If I hard-power-off the live node, then the other xenhost node starts up
> the guest, as you'd expect.
> 
> When, however, I turn the formerly-live node back on, the guest is
> stopped on the newer-live node, and started on the formerly-live node again.
> 
> I don't mind this moving, but I do mind that it's a stop-and-start
> rather than a migration. Can I stop this happening?

look up resource-stickiness in Pacemaker Explained

> 
> Thanks,
> 
> Matthew
> 
> node 739821491: on \
>        attributes type=quorum
> node 739821492: ophon \
>        attributes type=xenhost maintenance=off standby=off
> node 739821493: opus \
>        attributes type=xenhost maintenance=off standby=off
> primitive written Xen \
>        params xmfile="/etc/xen/written.csi.private.cam.ac.uk.cfg" \
>        meta allow-migrate=true target-role=Started \
>        op monitor timeout=30 interval=10 depth=0 \
>        op start timeout=60 interval=0 \
>        op stop timeout=40 interval=0
> location xenhosts written \
>        rule -inf: type ne xenhost
> property cib-bootstrap-options: \
>        dc-version=1.1.12-561c4cf \
>        cluster-infrastructure=corosync \
>        cluster-name=mwsv3 \
>        stonith-enabled=false \
>        last-lrm-refresh=1431619786
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org