Hi!
IMHO "dampening" was a very bad term, and it had confused me right from the
start.
Maybe "change_ignore_time" would have been better.
But actually a true moving average (over a fixed window) would be much
preferrable.
Maybe exponential averaging, too.
And the description in pingd is very poor
I found page https://clusterlabs.org/pacemaker/man/ only by accident.
There is no link from anywhere else in this site, at least I have not
found one. Logically I expect it to be linked from Documentation section.
___
Manage your subscription:
https://lis
On Wed, 2021-10-13 at 21:13 +, Janghyuk Boo wrote:
> Dear Community,
>
> I have a Pacemaker cluster with two cluster nodes with two network
> interfaces each, and two remote nodes and one fabric fencing agent
> for the whole cluster.
> nodelist {
>node {
>ring0_addr: xxx
>
Dear Community,
I have a Pacemaker cluster with two cluster nodes with two network interfaces each, and two remote nodes and one fabric fencing agent for the whole cluster.
nodelist { node { ring0_addr: xxx ring1_addr: xxx name: jangcluster-srv-1 nodeid: 1 } node {
In the ping resource script, there's support for "dampen" in the use of
attrd_updater.
My expectation is that it will cause "ping", "no-ping", "ping" to result in the
service being continually presented as up rather than to flap about.
In testing I can't demonstrate this, even using attrd_updat
