On 2007-07-16T11:05:07, Dominik Klein <[EMAIL PROTECTED]> wrote:
> First of all: If you do not want to have a monitor action in your custom
> RA, no one forces you to really implement one. The script should just
> not return an error when called with the monitor parameter.
This is incorrect, or at least incomplete.
Even if no "monitor" operation is configured, the cluster will do
startup probes to find out whether the resource is running somewhere and
in what state.
If those calls blindly return "no error" (ie, 0, success), the cluster
will go into multiple active recovery mode, which is not usually what
you want.
You _do_ want monitor to return the proper state of your resource.
The safe return code for those pseudo-resources like MailTo is
"OCF_NOT_RUNNING", but that should be done sparingly. It also means that
they'll not pass the ocf-tester script, but such is life.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
