On 10/29/07, Keisuke MORI <[EMAIL PROTECTED]> wrote: > Hi, > > >From the discussion of bugzilla #1722, > the behavior in the following situation is now changed > in the recent version. > > * When the second resource in a group failed and there is no node > available to run; > > 2.1.2: all resources in the group are stopped. > > obs-2.1.2-15: the second resource is stopped, but the first resource > is not stopped and continues to run. > > cf. http://old.linux-foundation.org/developer_bugzilla/show_bug.cgi?id=1722 > > Andrew told me that this is a bug fix and the 2.1.2's behavior was wrong. > > But for me (and my customers) this is a big and fundamental > change from the opearation point of view. > > > Andrew, > May I ask a favor of you; > > 1) Is it possible to modify to preserve the compatibility about > this behavior?
no > I think that the old behavior is preferable because running > "a part of the group" is pointless from the service > availability's point of view and confusing to users. no. just because items later in the group fail doesn't mean the rest of the group should be stopped. consider: IP + Filesystem + Apache + MySQL Just because MySQL fails doesn't mean Apache, the Filesystem nor the IP should be stopped. The PE is trying to keep as much of the cluster active as is legally possible^, nothing is gained by stopping the first child in your scenario. ^ Remember its a Highly Available cluster. > 2) If it would not be possible, then would you tell me > what is the "correct" configuration to achieve the same > result as 2.1.2 in the new version? > (with "correct" I mean "by design" and "unlikely change in > the near future") > > I'm also wondering how anybody else configures about this behavior. Let me instead ask what you believe you gain by stopping the first resource. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
