How can I set pacemaker cluster resources to start in order which are not necessarily colocated?
Issue
- Specific resource(s) which are configured to run only on one node are not starting because resource ordering is enforced.
- How can I customize the mandatory resource ordering feature in pacemaker cluster so that not all resources are required to be started?
- How can I enforce ungrouped resources to start first but without the default mandatory option where only one ungrouped resource remain in started state.
Environment
- Red Hat Enterprise Linux Server 6, 7 (with the High Availability Add On)
- pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
