[Pacemaker] ping resource polling skew

Andreas Kurz andreas at hastexo.com
Tue Mar 19 20:43:39 EDT 2013

On 2013-03-19 17:02, Quentin Smith wrote:
> Hi-
> I have my cluster configured to use a cloned ping resource, such that I
> can write a constraint that I prefer resources to run on a node that has
> network connectivity. That works fine if a machine loses its network
> connection (the ping attribute goes to 0, resources migrate to another
> machine, etc.).
> However, if instead what happens is the ping /target/ goes offline, it
> seems that Pacemaker will bounce resources around the cluster, as each
> node notices that the ping target is unreachable at a slightly different
> time.

using more than one targets is always a good idea and choose targets
that are also highly available

> Is there any way to get Pacemaker to delay resource transitions until at
> least one full polling cycle has happened, so that in the event of an
> outage of the ping target, resources stay put where they are running?

there is the "dampen" parameter .... use a high value like 3 or more
times the monitor-interval to give all nodes the chance to detect the
dead target(s), that should help.


Need help with Pacemaker?

> --Quentin
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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

More information about the Pacemaker mailing list