Red Hat Bugzilla – Bug 247980
RFE: (strong and weak) service dependencies
Last modified: 2009-04-16 16:22:32 EDT
+++ This bug was initially created as a clone of Bug #247783 +++
For SAP server systems, to be able to describe in which order e.g. the
underlying database and the SAP application server are started, a way to define
dependencies between services in the Cluster Suite is needed.
One service should be able to depend on multiple other services, e.g. an SAP
application service needs the database as well as its so-called central instance
These dependencies should be definable as "strong" or "weak" (or whatever
terminology fits best here). If service A depends on service B, "strong" would
mean that A must be stopped if B fails and started again when B recovers. "Weak"
would mean that A must be started after B is started but can recover by itself
if B fails during operation. For example, an SAP application server needs a
running DB to start (otherwise it bails out with an error message) but can
recover by itself if the DB fails and gets restarted. In this case it would
rollback unsaved transactions, but the user sessions would be preserved. If the
application server would get restarted in the event of a DB failure, all user
sessions would be lost which is quite undesirable.
-- Additional comment from email@example.com on 2007-07-11 09:22 EST --
Created an attachment (id=158945)
Patch against RHCS4 to implement dependencies between services
The patch I mailed to you ages ago which should implement dependencies between
services as an OCF script. It implements a "needs_recovery" flag which if true
would define a "strong" dependency or if false a weak one. Mind that I haven't
tested it thoroughly at that time and don't know if it is applicable to the
Set flags to propose for RHEL 4.7.
Pushed to RHEL4 git branch
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.