>>> Lars Marowsky-Bree <[email protected]> schrieb am 20.06.2012 um 15:56 in >>> Nachricht <[email protected]>: > On 2012-06-20T08:44:33, Ulrich Windl <[email protected]> > wrote: > > > > > The problem is: What to do if "1 out of n" exports fails: Is the > > > > resource > > > > > "started" or "stopped" then. Likewise for unexporting and monitoring. > > > If the operation partially failed, it is failed. > > > > But to have a "clean stopped", the resource has to be stopped again, even > though start failed (asuming the logic that a failed start operation leaves > the resource in "stopped" state). Likewise if the monitoring of a partially > started resource will report stopped, the resource is not really cleaned up. > So I guess your answer ist a bit too simple. > > That assumed logic is wrong. A failed start leaves the resource in a > failed state, hence causing it to be stopped (depending on the on-fail > policy for start, of course). > > A partially started/stopped resource's monitor also would need to report > failed.
Hi Lars, so what exit code is failed? Then: With the standard logic of "stop" only performing when the resource is up (i.e. monitor reports "stopped"), a partially started resource that the monitor considers "stopped" may fail to be cleanly stopped on "stop". > > My answer is not too simple - I said "failed", not "stopped" ;-) Maybe if you could present a skeletton of code for a resource that can fail partially, we could be more concrete... Regards, Ulrich _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
