Bug 679615 - Implement hardrecovery
Summary: Implement hardrecovery
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager
Version: 5.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 00:29 UTC by Lon Hohberger
Modified: 2012-02-10 17:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-10 17:28:15 UTC
Target Upstream Version:


Attachments (Terms of Use)
Preliminary patch; unit-tested but not reviewed. (2.62 KB, patch)
2011-02-23 00:29 UTC, Lon Hohberger
no flags Details | Diff

Description Lon Hohberger 2011-02-23 00:29:44 UTC
Created attachment 480302 [details]
Preliminary patch; unit-tested but not reviewed.

Description of problem:

In some cases, it is desirable for resource agents to be able to time out or otherwise fail.  Typically, rgmanager places services where this occurs into the failed state.  This state requires administrative intervention in order for the service to exit this state.

Some resource-agents have a magic "self_fence" attribute, but this can fail for a variety of reasons - the most obvious one being use of queueing mechanisms when all paths fail to a given piece of storage.

In some cases, such as using HA-LVM with mirrored volume groups, there is a possibility for deadlock, causing self_fence to never be triggered.

The "hardrecovery" parameter could be used in conjunction with __enforce_timeouts in order to cause a failed -or- timed-out stop operation for a hung resource agent to cause the machine to reboot.

Version-Release number of selected component (if applicable): 2.0.115-68.el5


Note You need to log in before you can comment on or make changes to this bug.