On Mon, Oct 25, 2010 at 7:49 AM, Junko IKEDA <tsukishima...@gmail.com> wrote: > or would it better not to increment the failcount? > in unpack_rsc_op(), demote operation is checked not to go into loop, > but promote is not. > see attached.
the role remains correct though, and the location constraint causes the resource to be stopped. would it not be better to send a demote op and see if it can operate as a slave? > > Thanks, > Junko > > 2010/10/21 Junko IKEDA <tsukishima...@gmail.com>: >> Hi, >> >> When the promote/demote action returns error code, >> it seems that failcount isn't incremented, >> so promote/demote action would go into a loop in some cases. >> Default settings for promote/demote are implicitly-defined >> (on_fail="restart" and interval=0). >> Is it possible to handle them as in the case of start/stop operation? >> It means, if there are some errors about promote/demote, >> pacemaker considers its interval as 1 temporarily. >> see attached. >> >> Thanks, >> Junko IKEDA >> >> NTT DATA INTELLILINK CORPORATION >> > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
