non-critical behavior does not work when __independent_subtree applied to service in RHEL 4, 5, or 6 cluster
Issue
-
As per requirement that the DB not relocate when it fails, I configured the `
as follows: <service autostart="1" domain="prefer`" name="dbservice" __independent_subtree="2" recovery="relocate" >
But the service is still relocating when the DB fails.
Environment
- Red Hat Enterprise Linux Server 5 (with the High Availability or Resilient Storage Add Ons)
- Red Hat Enterprise Linux Server 6 (with the High Availability or Resilient Storage Add Ons)
- Red Hat Cluster Suite
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.