im trying to understand the behaviour of pacemaker when a resource monitor returns OCF_NOT_RUNNING instead of OCF_ERR_GENERIC, and does pacemaker really care.
The documentation states that a return code OCF_NOT_RUNNING from a monitor will not result in a stop being called on that resource, as it believes the node is still clean. https://www.clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html This makes sense, however in practice is not what happens (unless im doing something wrong :) ) When my resource returns OCF_NOT_RUNNING for a monitor call (after a start has been performed) a stop is called. if I have a resource threshold set >1, i get start->monitor->stop cycle until the threshold is consumed /Ian.
_______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.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