On Mon, May 2, 2011 at 8:27 AM, Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> wrote: >>>> Andrew Beekhof <and...@beekhof.net> schrieb am 29.04.2011 um 09:31 in >>>> Nachricht > <BANLkTi=-ftyk9uxcgu0m2wqhquu_rt8...@mail.gmail.com>: >> On Fri, Apr 29, 2011 at 9:27 AM, Dominik Klein <d...@in-telegence.net> wrote: >> > It waits $dampen before changes are pushed to the cib. So that >> > eventually occuring icmp hickups do not produce an unintended failover. >> > >> > At least that's my understanding. >> >> correcto > > Hi! > > Strange: So the update is basically just delayed by that amount of time? I > see no advantage: If you put a bad value to the CIB immediately or after some > delay, the value won't get better by that. "Damping" siggests some filtering > to me, but you are saying your are not filtering the values, but just > delaying them. Right?
Only the "current" value is written. So the cluster will tolerate "minor" outages provided they last for less than the dampen interval and the monitor frequency is high enough. _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
