try to use on-fail for single resource. 2016-03-25 0:22 GMT+01:00 Adam Spiers <[email protected]>: > Sam Gardner <[email protected]> wrote: >> I'm having some trouble on a few of my clusters in which the DRBD Slave >> resource does not want to come up after a reboot until I manually run >> resource cleanup. >> >> Setting 'start-failure-is-fatal=false' as a global cluster property and a >> failure-timeout works to resolve the issue, but I don't really want the >> start failure set everywhere. >> >> While I work on figuring out why the slave resource isn't coming up, is it >> possible to set 'start-failure-is-fatal=false' only on the DRBDSlave >> resource, or does this need a patch? > > No, start-failure-is-fatal is a cluster-wide setting. But IIUC you > could also set migration-threshold=1 cluster-wide (i.e. in > rsc_defaults), and then override it to either 0 or something higher > just for this resource. You may find this interesting reading: > > https://github.com/crowbar/crowbar-ha/pull/102/commits/de94e1e42ba52c2cdb496becbd73f07bc2501871 > > _______________________________________________ > Users mailing list: [email protected] > 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
-- .~. /V\ // \\ /( )\ ^`~'^ _______________________________________________ Users mailing list: [email protected] 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
