Why did a cluster service using a failoverdomain with nofailback="0" relocate to another node when it joined the cluster in RHEL?

Solution Verified - Updated -

Issue

  • When a node joined the cluster, a service relocated to it
  • When I started rgmanager on a node without issuing any other commands, the service "recovered".

Environment

  • Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
  • Red Hat Cluster Suite (RHCS) 4
  • rgmanager
  • A service using a failoverdomain with nofailback="0" (or nofailback unset), orderered="1", and nodes with different priority scores, such as:
            <failoverdomain name="prefer-node1" nofailback="0" ordered="1" restricted="1">
                <failoverdomainnode name="node1" priority="1"/>
                <failoverdomainnode name="node2" priority="2"/>
            </failoverdomain>

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