Can I configure a constraint so that one resource always runs on a different node from another resource in a RHEL 6 or 7 High Availability cluster with pacemaker?
Issue
- We require two resources in
pacemakerbut they never should be allowed to run on the same system and if one system is ever physically down that resource is also not allowed to be migrated onto the running system. - How to configure two resources in a way that ensures some kind of "anti-affinity" or allow the resource to be down on the standby node if the node is physically off?
- Does
pacemakeroffer "anti-colocation" constraints? How do I configure one?
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- Two or more resources in which one must never run on the same node as another
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.