- **status**: unassigned --> assigned
- **Milestone**: future --> 4.7-Tentative
---
** [tickets:#315] SU restart not according to spec**
**Status:** assigned
**Milestone:** 4.7-Tentative
**Created:** Fri May 24, 2013 08:35 AM UTC by Nagendra Kumar
**Last Updated:** Tue Jun 25, 2013 11:57 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/3061
First issue:
=====================
When testing http://devel.opensaf.org/ticket/3056 I found the problem that SU
restart does not follow the instantiation level as supposed to:
spec 3.8.2
"Within a service unit, the Availability Management Framework terminates the
pre-instantiable components according to the configured instantiation level.
All pre-instantiable components with the same instantiation level are
terminated by the Avail-
ability Management Framework in parallel. Pre-instantiable components of a
given level are only terminated by the Availability Management Framework when
all pre-instantiable components with a higher instantiation level have been
terminated.
As has been said previously, the instantiation level is only applicable during
service unit instantiation and termination. As restarting a service unit means
terminating the
service unit and instantiating it again, the instantiation level also applies
when restart-ing a service unit."
It is obvious from the code in avnd_su_pres_inst_surestart_hdler():
/*
•If pi su, pick the first pi comp & trigger it's FSM with RestartEv?. */
if (m_AVND_SU_IS_PREINSTANTIABLE(su)) {
TRACE("PI SU:'%s'",su->name.value);
for (curr_comp =
m_AVND_COMP_FROM_SU_DLL_NODE_GET(m_NCS_DBLIST_FIND_FIRST(&su->comp_list));
should pick the last component since this list is sorted by the instantiation
level.
Second issue:
================
3.11.1.2:
"Restarting a service unit is achieved by the following actions:
• First, all components in the service unit are terminated in the order
dictated by their instantiation-levels.
• In a second step, all components in the service unit are instantiated
in the order dictated by their instantiation-levels."
That is not the case today since each component is restarted (not terminated
and instantiated)
---
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.------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
