On 7 Feb 2014, at 8:54 pm, Frank Brendel <frank.bren...@eurolog.com> wrote:
> >> Its somewhat inferred in the description of cluster-recheck-interval >> >> cluster-recheck-interval = time [15min] >> Polling interval for time based changes to options, resource >> parameters and constraints. >> >> The Cluster is primarily event driven, however the configuration >> can have elements that change based on time. To ensure these changes take >> effect, we can optionally poll the cluster's status for changes. Allowed >> values: Zero disables polling. Positive values are an interval in seconds >> (unless other SI units are specified. >> eg. 5min) >> >> the failure-timeout doesn't result in any events on its own, so the >> reprocessing happens the next time the PE gets kicked by the recheck timer. >> >> > > On the other hand, does it mean if cluster-recheck-interval is 0 the > failure-timout is handled only when a cluster event (other resource failures, > changing configuration etc.) occurs? yes
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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://bugs.clusterlabs.org
