Matthew Vernon <[email protected]> writes: > Hi, >
> > Why, if I have specified that my resource "written" is only to be run on > "xenhost" nodes is the cluster trying to monitor it on the quorum node? > Better, how can I stop it doing so (or, if that's impossible, suppress > the errors)? First off, yes, it does so to ensure that the resource isn't running where it shouldn't be. These monitor operations are referred to as probes in the documentation. The location constraint is not enough for pacemaker to know that the resource is not supposed to be runnable on that node. I seem to recall that it's possible to turn this off in recent versions of pacemaker, but I can't recall exactly how. Maybe someone else can help you with that.. Another option is to modify the resource agent and check in the monitor action if this is the probe (ocf_is_probe). In that case, the monitor action should return OCF_NOT_RUNNING rather than OCF_ERR_INSTALLED on those nodes where the resource is not supposed to run. -- // Kristoffer Grönlund // [email protected] _______________________________________________ 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
