AMF Spec Section 220.127.116.11 Does Not Appear to be Adhered To
(Doc ID 1644534.1)
Last updated on APRIL 24, 2014
Applies to:Oracle Communications OpenSAFfire - Version 6.3.0 and later
Information in this document applies to any platform.
The AMF Specification Section 18.104.22.168 does not appear that it is being adhered to, According to the spec, once the number of component restarts reaches the maximum, the SU restarts begin. The spec says:
During the "service unit restart" probation period, each error report on the service unit with an SA_AMF_COMPONENT_RESTART recommended recovery action immediately escalates the recovery to an entire service unit restart (as level 1 escalation is active).
When the "service unit restart" probation period starts, the Availability Management Framework also starts counting the number of times it has to perform a level 1 escalation.
If this count does not reach the saAmfSGSuRestartMax value before the end of the "service unit restart" probation period (the duration of the period is specified by saAmfSGSuRestartProb), the "service unit restart" probation period for the affected service unit expires.
If this count reaches the saAmfSGSuRestartMax value before the end of the "service unit restart" probation period, the Availability Management Framework performs the second level of recovery escalation for that service unit: the Availability Management Framework fails over the entire service unit and terminates the "service unit restart" probation period.
The Customer has a simple application with one SU and two components. CompRestartMax is 0, so any failed components automatically trigger SU restarts. Any further component failures should trigger SU restarts.
In this case, kill both components at the same time, which should trigger two SU restarts. Instead, the SU fails over after one SU restart.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document