Bug 149345
Summary: | service/device failure leads to uncontrolled fail overs | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Dean Elling <dean.elling> |
Component: | clumanager | Assignee: | Lon Hohberger <lhh> |
Status: | CLOSED WONTFIX | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | cluster-maint, rkenna |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-02 16:05:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 169576 |
Description
Dean Elling
2005-02-22 17:10:03 UTC
Please file a ticket with Red Hat Support so this is properly tracked. It sounds like a generally useful feature. This is possible if we split up the serviceblock structure's two uint16_t around restarts / checks into two uint8_t. We could add a max_faults - which would disable the service after so many restarts (unlike max_restarts which merely relocates the service to another node after the count is exceeded). This would be difficult to implement while preserving rolling upgrade and not breaking the on-disk format of service states. |