Failover domain priority doesn't get honoured when relocating service manually with `clusvcadm` command

Solution Verified - Updated -

Issue

Cluster service is configured to run in following failover domain:

<failoverdomain name="failoverXYZ" nofailback="1" ordered="1" restricted="0">
                                <failoverdomainnode name="node1" priority="1"/>
                                <failoverdomainnode name="node2" priority="2"/>
                                <failoverdomainnode name="node3" priority="3"/>
</failoverdomain>

Based on the above configuration the service should primarily run on node1 and should relocate to node 2 when relocation is required. When clusvcadm -r <service> is executed sometimes service relocates to node3 which is not expected as per the priority . Why service relocates randomly?

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • High Availability cluster (based on rgmanager)

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