Actually avnd_su_pres_restart_compinst_hdler was called to pick the next csi,
but no csi has been found si_dll_node
---
** [tickets:#885] Not all npi-components are restarted during SuRestart
escalation**
**Status:** unassigned
**Milestone:** future
**Labels:** NPI SU escalation
**Created:** Tue May 06, 2014 06:14 AM UTC by Minh Hon Chau
**Last Updated:** Tue May 06, 2014 06:14 AM UTC
**Owner:** nobody
Changeset: 4412, 5216
model: NwayActive
configuration:
- 1 App, 1 SG, 2 SUs hosted in PL-3/PL-4, 15 npi-comps per SU, 2 SIs with 15
CSIs for each SI
- saAmfSgtDefCompRestartProb: 2000000
- saAmfSgtDefCompRestartMax: 3
Tests:
pkill {all comps}
Problem:
A few of components are restarted
Initial Analysis:
During su restart, in avnd_su_pres_inst_surestart_hdler(), amfnd currently
picks only one csi in the csi_list to initiate the restart for corresponding
component of this csi, that will miss the graceful restart of the rest
components.
---
Sent from sourceforge.net because [email protected] 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.------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
