How to Stop a Resource to Failback to Original Node after It Starts on Another Node in Corosync and Pacemaker Cluster
(Doc ID 2522874.1)
Last updated on APRIL 24, 2020
Applies to:Linux OS - Version Oracle Linux 7.3 with Unbreakable Enterprise Kernel [3.8.13] and later
Say there is a resource running in a Corosync and Pacemaker cluster and it is started on another node after the original node goes down unexpectedly.
When the original node comes back online, to stop that resource to failback, below solution can be tried.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document