Is there a way to mark a pacemaker resource or `colocation` constraints as non-critical or critical?
Issue
- Is there a way to mark a pacemaker resource or
colocationconstraints as non-critical or critical? - In pacemaker there currently isn't way to configure
__independent_subtree="2" and __max_restarts="n"as it is in rgmanager based clusters. Is there a plan to include it in pacemaker?
Environment
- Red Hat Enterprise Linux 8
- Pacemaker cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
