Hi Minh,
Since this ticlet is marked fixed, we need to document some discussed
conclusion (limitation) where application will not be recovered. These were
based on following cases discussed in this ticket.
1)When ssytem bcomes headless When AMFD sends some assignment message because
of admin operation or recovery from fault but message does not reach to AMFND.
2)Similarly when AMFND seds some assignment response but it does not reach to
AMFD as system becomes headless.
These were the cases where AMFD may require to self trigger the FSM which is
not possbile today.. Also there were cases where AMFD could not update IMM for
attributes like SG FSM state and SUSI FSM state etc and system become headless.
IN this case also recovery is not possible after headless.
---
** [tickets:#1725] AMF: Recover transient SUSIs left over from headless**
**Status:** fixed
**Milestone:** 5.1.FC
**Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau
**Last Updated:** Mon Sep 19, 2016 04:08 AM UTC
**Owner:** nobody
This ticket is more likely an enhancement that targets on how AMFD detect and
recover the transients SUSI left over from headless. There are three major
situations:
(1) - Cluster goes headless, su/node failover on any payloads can happen, or
any payloads can be hard rebooted/powered off by operator, then cluster recover
(2) - issue admin op on any AMF entities, cluster goes headless. During
headless, the middle HA assignments of whole admin op sequence between AMFND
and components could be:
(2.1) The assignment completes, component returns OK with csi callback,
then cluster recover
(2.2) The assignment is under going, then cluster recover. The assignment
afterward could complete, or csi callback returns FAILED_OPERATION or error can
also happen
At the time cluster recover, amfd has collected all assignments from all
amfnd(s). These assignments can be in assigned or assigning states whilst its
HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen
in a combination, which means while issuing admin op (2), cluster go headless
and any kinds of failover (1) can happen during headless.
---
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.------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
