An 'unmanaged' pacemaker resource monitor failure can trigger recovery to occur
Issue
- The cluster service is having
SAPDatabase
resource which was set asunmanaged
, but stillpacemaker
was performing monitor operations on it which had caused a resource failure and triggered a service relocation. - Resource is unmanaged but cluster still moved it when it failed 3 times
- After marking a resource as
unmanaged
, is it also required to manually disable monitoring on it?
Environment
- Red Hat Enterprise Linux 7 with High Availability Add-Ons
- Red Hat Enterprise Linux 6.5 with High Availability Add-Ons
pacemaker
cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.