Hi,
Something is triggering a new transition. The most likely candidate is
a low value for cluster-recheck-interval.
Many years ago, a low cluster-recheck-interval was necessary to make
certain things like failure-timeout more timely, but that has not been
the case in a long time. It should be
Hello all,
I am managing a cluster using pacemaker for high availability. I am parsing the
logs for relevant information on the cluster health and the logs are full of
the following:
```
Nov 29 09:17:41 esvm2 pacemaker-controld[2893]: notice: State transition
S_IDLE -> S_POLICY_ENGINE
Nov 29
Hello,
I deployed a Lustre cluster with 3 nodes (metadata) as pacemaker/corosync
and 4 nodes as Remote Agents (for data). Initially all went well, I've set
up MGS and MDS resources, checked failover and failback, remote agents were
online.
Then I tried to create a resource for OST on two nodes
