Resource relocates back to its original node even though there is a resource-stickiness value configured in a RHEL 6 or 7 High Availability cluster with pacemaker
Issue
- After a node is fenced, its resources relocate to another node as expected. But when that node rejoins, the resources move back to it, even though we've configured a
resource-stickinessvalue - I have a default
resource-stickinessconfigured, but resources still move back to the original node. Why? - Will a
resource-stickinesssetting with a finite value be overridden by a location constraint with a score ofINFINITY?
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- One or more resources configured with a location constraint
<cib><configuration><constraints><rsc_location/></constraints></configuration></cib>in the cluster CIB
- One or more resources configured with a
resource-stickinessvalue, either directly on the resource, through a cluster-wide resource default, or through the cluster propertydefault-resource-stickiness.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.