[Pacemaker] disable migration after the faicount

[Andrew Beekhof]

On 26 Nov 2013, at 11:55 pm, ESWAR RAO <eswar7028 at gmail.com> wrote:

> Hi All,
> 
> Even I tried with meta allow-migrate="false", but still the resource is migrating to another node.

I think you mean "move" - aka. "stopped here and started there".
In which case you need to use a location constraint (with score=-INFINITY) to disallow the other node from hosting the resource.
Combine that with migration-threshold=3 and it should do what you're after.

> 
> Thanks
> Eswar
> 
> 
> On Tue, Nov 26, 2013 at 12:55 PM, ESWAR RAO <eswar7028 at gmail.com> wrote:
> Hi All,
> 
> Can someone help me in the below configuration??
> 
> primitive oc_graphite lsb:graphite \
>         meta allow-migrate="true" migration-threshold="3" failure-timeout="30s" \
>         op monitor interval="5s" timeout="20s"
> 
> With a resource like above, I was able to migrate the resource to another node after 3 failures within a timeout window of 5sec.
> 
> I want to set up a configuration like, pacemaker will not migrate the resource instead it will not monitor/act on the resource after 3 failures within the timeout window.
> 
> I saw "is-managed" flag but it doesn't restart the resource even after the 1st failure.
> 
> Thanks
> Eswar Rao
> 
> 
> _______________________________________________
> 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://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140108/a0d51c5c/attachment-0002.sig>