pcs resource move does not have any effect when resource-stickiness=INFINITY is configured for a resource in a Pacemaker cluster

Solution Verified - Updated -

Issue

  • When running the move command, it does not trigger the move at all. It creates a new location constraint , which will take affect during the next 'enable' of the group.
  • Is there any other way to disable autofailback of a group? If yes, how to do it?
  • After configuring pacemaker cluster, failed to disable the auto-failback feature? Whenever a node which runs the service getting fail, service get relocated to passive node successfully but when the original node comes back, the service will relocate (failback) to that node again. Looking for a way to configure the resource group such that, in case of node failure/crash resource group should get relocated to passive node and continue to run on the same node and should not failback to original node

Environment

  • Red Hat Enterprise Linux (RHEL) 6, 7, or 8 (with the High Availability Add-on)
  • Pacemaker
  • One or more resources configured with resource-stickiness=INFINITY

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In