Hi,
Andrew Beekhof wrote:
On 4/19/07, Peter Kruse <[EMAIL PROTECTED]> wrote:
The point is: the _meaning_ of probe is different to monitor:
no, its not. trust me :-)
what do you mean? of course it's different!
both ask the same question: "Is this resource running?"
yes, but the consequence to this question is different,
depending on the answer:
on the one hand, "running" can mean heartbeat has to stop it,
because it shouldn't be running
on the other hand, "running" has no consequence because
that's how it's supposed to be.
on monitor, if the resource is running then it's ok
on probe, it is generally not ok in the sense that it's
generally not what you want.
That means, maybe you want your RA to log a message
when called as "probe" to write something like:
"Resource is running although it shouldn't"
probes don't only happen at startup so this assumption does not hold
That's exactly the problem, the RA should find out
when to log the correct message. Example:
On startup, when the probe is called, all (our) RAs
log error messages like
"ERROR! ERROR! Apache is not running!"
which is wrong and confusing, because it's not
an error at this stage. It should log a different
message that don't alert an admin.
I hope you can agree to that.
but when called as "monitor" you would probably
log nothing on success.
Convinced?
nope :-)
still not?
Peter
_______________________________________________
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
