Hi Andrew, > Do you mean: why is the clone on srv01 always $clone:0 but on srv02 > its sometimes $clone:0 and sometimes $clone:1 ?
yes. The replacement thought both nodes to be the same movement. Because it is "globally-unique=false"..... Best Regards, Hideo Yamauchi. --- Andrew Beekhof <and...@beekhof.net> wrote: > 2010/3/24 <renayama19661...@ybb.ne.jp>: > > Hi Andrew, > > > > Thank you for comment. > > > >> So if I can summarize, you're saying that clnUMdummy02 should not be > >> allowed to run on srv01 because the combined number of failures is 6 > >> (and clnUMdummy02 is a non-unique clone). > >> > >> And that the current behavior is that clnUMdummy02 continues to run. > >> > >> Is that an accurate summary? > > > > Yes. > > > >> If so, then I agree its a bug. \xA0Could you create a bugzilla entry for > >> it please? > > > > I understood. > > I register this problem in Bugzilla. > > Thanks > > > How about my next question? > > Is the difference of the replacement of the clone in N1 and N4 > > specifications? > > > >>Of a clone rising in a N1(srv01) node at the time of > >>"globally-unique=false" is replacing it > right? > >>In addition, is it right movement that replacement does not happen even if > >>a clone breaks down > in a > > N4(srv04) node? > > Do you mean: why is the clone on srv01 always $clone:0 but on srv02 > its sometimes $clone:0 and sometimes $clone:1 ? > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker >
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
