Changing the totem token timeout value of a cluster is not making any effect and node is getting fenced before the set timeout value
Issue
- A node in the cluster is getting fenced with "[TOTEM ] A processor failed, forming new configuration" messages. This issue continued even after changing the totem token timeout to higher value in
corosync.conf
file and propagating it to rest of the nodes withpcs cluster sync
command. - Changes in
token
attribute value of the corosync configuration are not getting reflected in cluster.
Environment
- Red Hat Enterprise Linux Server release 6,7,8 or 9 with High Availability Add-On
- pacemaker
- corosync
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.