Resource groups in RHEL 7 Pacemaker clusters can migrate back to previously failed nodes automatically when resource-stickiness=INFINITY is set on multiple resources in the group, or default resource-stickiness is set to INFINITY

Solution Verified - Updated -

Issue

When setting resource-stickiness=INFINITY, it is anticipated that if a resource group is forced away from a node it will be unable to migrate to that node unless it is the only node available or it is forced to do so manually. In circumstances where the default resource-stickiness=INFINITY or resource-stickiness=INFINITY is set on multiple resource in the group, resource groups with multiple resources can unexpectedly migrate to nodes they have previously moved away from even if there are other more preferable nodes available.

Environment

  • Red Hat Enterprise Linux Server 7, 8, 9 (with the High Availability Add On)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content