Rgmanager service fails over when node rejoins cluster on Red Hat Enterprise Linux
Issue
- when i have started cluster on node1 (node was running outside the cluster while we were investigating another problem), it took over resources from node2 and caused an outage
- I have started cluster services (including rgmanager) on node1. At that time the cluster service was running on node2. Both nodes have the same failover domain priority and nofailback="0" so there was no reason for cluster service to failover to node1, however it did. The question is WHY?
Environment
- Red Hat Enterprise Linux (RHEL), including:
- Red Hat Enterprise Linux Server 5 (with the High Availability and Resilient Storage Add Ons)
- Cluster with 2 or more nodes.
- One cluster node rejoins the cluster, and upon starting rgmanager, a service "fails over" to that node
- failover domain for the service is not
orderedand the service has settingnofailback="0", meaning the service should not relocate to higher priority nodes.
- failover domain for the service is not
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
