Oracle Linux: How to Prevent a Resource From Failing Back to its Original Location Automatically when Preferred Node Rejoins Pacemaker Cluster? (Doc ID 2977070.1)

Last updated on NOVEMBER 07, 2023

Applies to:

Goal

When Node1 is rebooted, resources are getting moved to Node2 or Node3 as expected.

Once the Node1 is back online, resources are getting back (failback) to Node1.

The primary node (Node1) is fenced and rejoins the cluster after a reboot, application suffers another outage when the cluster fails the resource back to the primary node (Node1)

How to prevent a resource group to move twice?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.