Out of the two problems reported in this issue, one problem:
"Component is disabled during restart recovery" got fixed in
changeset: 4176:3d28b7015bf0
branch: opensaf-4.2.x
parent: 4173:ca88d7a8749b
user: Hans Feldt <[email protected]>
date: Fri Apr 12 13:00:34 2013 +0200
summary: avsv: treat comp quiesced errs as other errs (#3083)
---
** [tickets:#358] AMF SU/component state computation issues when restarting**
**Status:** assigned
**Milestone:** 4.3.3
**Created:** Fri May 31, 2013 03:22 AM UTC by Nagendra Kumar
**Last Updated:** Mon Jun 16, 2014 11:30 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/1725
When a component is restarted via the COMPONENT_RESTART recovery policy and
restart is enabled for the component, there are a number of AMF SU and
component state computation issues observed:
1. SU does not enter restarting presence state when single member component
enters restarting presence state.
Changes in member component presence states should always trigger a
re-calculation of the SU's presence state and in this case should have led to
the SU's presence state changing to restarting.
2. Component enters the disabled operational state (which also triggers
out-of-service readiness state transition) when it should remain enabled.
In the case of a component restart recovery operation, a component should not
be considered disabled since that would imply the removal of the CSI
assignments from the component. In addition, if the sole member component is in
the disabled operational state then the SU should also be in the disabled
operational state which it is not.
The following are the state transitions from the AMFD trace file for an SU and
component that demonstrate these issues (ignore the gaps in the timestamps):
Jan 28 8:09:50.425882 osafamfd [28028:avd_su.c:0660] >> avd_su_pres_state_set:
'safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' INSTANTIATING => INSTANTIATED
Jan 28 8:18:14.659529 osafamfd [28028:avd_comp.c:0085] >>
avd_comp_pres_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' INSTANTIATED =>
RESTARTING
Jan 28 8:18:14.660422 osafamfd [28028:avd_comp.c:0103] >>
avd_comp_oper_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' ENABLED => DISABLED
Jan 28 8:18:14.660863 osafamfd [28028:avd_comp.c:0119] >>
avd_comp_readiness_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' IN_SERVICE =>
OUT_OF_SERVICE
Jan 28 8:18:44.750580 osafamfd [28028:avd_comp.c:0103] >>
avd_comp_oper_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' DISABLED => ENABLED
Jan 28 8:18:44.750900 osafamfd [28028:avd_comp.c:0119] >>
avd_comp_readiness_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' OUT_OF_SERVICE =>
IN_SERVICE
Jan 28 8:18:44.751273 osafamfd [28028:avd_comp.c:0085] >>
avd_comp_pres_state_set:
'safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1' RESTARTING =>
INSTANTIATED
Aside from the issues of compliance with the AMF specification and state model
coherency and its affect on AMF failover processing that come out of this
defect, there is also the fact that since the SU is not entering the restarting
state the SU presence state change notification is not being generated as
expected for this presence state transition. This is a useful notification for
users to monitor for and thus should be generated if an SU enters the
restarting, as the SU in this case should have.
Reproduction procedure:
0. Enable AMFD trace output
1. Startup cluster with 2N AMF sample configured (one component per SU)
2. Start the ntfsubscribe utility
3. Once AMF components are started and assigned workload, kill one of the AMF
component processes
4. Note that there is SU presence state change notifications generated for the
transition to the restarting state and then the transition back to the
instantiated presence state.
5. Review the AMFD log and note the transitions of the component and SU are not
as expected.
Changed 2 years ago by nagendra ¶
â– milestone set to 4.2.GA
SU FSM need to be changed and tested for single component getting restarted and
making SU to restart. Will require good amout of effort. So, pushing it into
next release.
---
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.
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
