- **status**: assigned --> unassigned
- **Blocker**: --> False
---
** [tickets:#178] escalation policy is not happening till the restart count
exceeds, instead of reaching saAmfSGCompRestartMax for NPI components**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar
**Last Updated:** Tue Sep 20, 2016 06:04 PM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2144
error escalation is not happening till the restart count exceeds
saAmfSGCompRestartMax for the components brought up in NPI.
But according to spec, first level escalation should happen when the restart
count reaches the saAmfSGCompRestartMax
Mentioned in the spec, 3.11.2.2 page NO: 203,
If this count reaches the saAmfSGCompRestartMax value before the end of the
"component restart" probation period, the Availability Management Framework per-
forms the first level of recovery escalation for that service unit: the
Availability Man-
agement Framework restarts the entire service unit
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
