I was wondering if it would be possible to introduce a new resource state, in addition to those already existing in the OCF specifications (like 0: no error, 1:succes), to indicate a resource is in a "busy" or in a "(in) transition", or in a "recovery" or "healing" or "autofix" state, typically when, while in some kind of maintenance or recovery situation (fsck'ing a filesystem or rebuilding the indexes of a database) it can not be started, but if an error staus was returned, an error counter would increment that could possibly exclude that resource from being used again without manual intevention.
When receiving such a "busy" state, pacemaker, when left without a failover option for that resource, whould regularly probe thois resource, over and over again, until the probe returns a "error", where it fails the resource, or a "success" where, if the resource is stopped, allows pacemaker to start the resource when it thinks it needs to. Thank you all for your comments on the matter. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
