- **status**: unassigned --> assigned
- **assigned_to**: Praveen
- **Part**: - --> nd



---

** [tickets:#538] AMF: fail-over assignments despite comps in TERM-FAILED 
state**

**Status:** assigned
**Milestone:** 5.0.2
**Created:** Fri Aug 09, 2013 06:43 AM UTC by Hans Feldt
**Last Updated:** Tue Sep 20, 2016 06:04 PM UTC
**Owner:** Praveen


AMF currently performs fail-over recovery action although a component is in 
termination-failed presence state. This can lead to severe inconsistencies for 
the application. The specification also clearly states how this should work in 
4.8:

"If the component and any of its contained components (for a container 
component)
were assigned the active HA state for some component service instances when the
CLEANUP command was executed, and semantics of the redundancy model of its
enclosing service group guarantee that at a point in time only one component 
can be
in the active HA state for a given component service instance, the failure to 
terminate
that component prevents the Availability Management Framework from assigning to
another component the active HA state for these component service instances (and
by the same token prevents the assignment of the active HA state to other 
service
units for the service instances that contain the involved CSIs). In this case, 
the ser-
vice instances will stay unassigned until an administrative action is performed 
to ter-
minate the failed component."

Can be tested by running the AMF 2N sa-aware sample app and modifying the 
cleanup script to do "exit 1" which gives this effect when the active component 
is killed:

Aug  9 08:40:01 Vostro osafamfnd[11307]: NO 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 
'avaDown' : Recovery is 'componentRestart'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Cleanup of 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Reason:'Exec of script success, but 
script exits with non-zero status'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Exit code: 1
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Component Failover trigerred for 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1': Failed component: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => 
TERMINATION_FAILED
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 
'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 
'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 
'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro amf_demo[11620]: CSI Set - HAState Active for all 
assigned CSIs
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 
'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Removing 
'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 08:40:01 Vostro osafamfnd[11307]: NO Removed 
'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'



---

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

Reply via email to