> we run "probes" on new cluster nodes...
> to make sure no service can ever be running twice
>> In other words, before starting a resource on a
>> node, for the first time after it's reboot, can
>> we assume HB always calls a "MONITOR" or a
>> "STOP" to certify no sub-resources used by that
>> resource are already allocated ?
> sub-resources?
Other system resources (not declared as CRM resources)
on which a CRM resource depends upon to start, and
that are verified at execution of the RA's MONITOR for
a "running healthy" status to be returned.
>> BTW is it a "MONITOR" or a "STOP" that is
>> first called by HB for a resource ?
So if I provide a MONITOR function in the RA, I assume
it will be a MONITOR that will be performed as
"probe".
What if I provide several MONITOR functions, of
different check levels, which check level will be
performed as "probe" ?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
