max_restarts or __max_restarts is configured on a service or resource but doesn't seem to be honored in a RHEL 5 or 6 High Availability cluster with rgmanager

Solution Unverified - Updated 2014-12-15T20:12:17+00:00 -

Issue

I've set __max_restarts on my __independent_subtree resource, but when I test failing that resource, it doesn't seem to change the bheavior after that limit is reached
My service is configured with a restart recovery policy and max_restarts is set, but the service doesn't relocate after that number of restarts like I expect
Do I need to set __restart_expire_time on a resource in addition to __max_restarts?
Do I need to set restart_expire_time on a service in addition to max_restarts?

Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
rgmanager
One or more services or resources configured to have a maximum number of restarts
- A service has maximum restarts specified without restart_expire_time in the form of <service recovery="relocate" max_restarts="<value>"> in /etc/cluster/cluster.conf, or
- A resource has maximum restarts specified without __restart_expire_time in the form of <<resource> __independent_subtree="(1|2)" __max_restarts="<value>"> in /etc/cluster/cluster.conf

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.