pacemaker-controld takes 1 second to request start operation of a critical resource when a peer node is lost
Issue
Is there any other way to make pacemaker-controld to request moving of VirtualIP resources faster than 1 second in a peer lost situation?
Environment
Red Hat Enterprise Linux 9 (with the High Availability Add-On)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
