- **Milestone**: 4.6.2 --> 4.7.2


---

** [tickets:#1542] AMF : Quiesced callbacks should be generated, during 
recovery (su failover flag disabled)**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue Oct 13, 2015 10:33 AM UTC by Srikanth R
**Last Updated:** Mon Nov 02, 2015 09:06 AM UTC
**Owner:** nobody


Changeset : 6901
Application : 2n 
                 4 SIs configured with SI1 as sponsor for SI2,SI3,SI4
                 Component recovery policy - 3
                 sufailoverflag -0

Steps :

 * Initially all the SIs are in unassigned state. SU1 is hosted active and SU2 
is hosted standby
 * Performed lock on SI4.
 * Later performed unlock on SI4, for which component in SU1 rejected the 
active callback.
 * As part of recovery, all the assignments to SU1 should be removed and active 
assignments to be given to standby su .i.e SU2.
 * In the current implementation, quiesced callbacks are not generated during 
removal of assignments.  
 * According to the spec page NO ;195, 

If the service unit is configured to fail over as a single entity 
(saAmfSUFailover
set to SA_TRUE), all other components of the service unit are abruptly termi-
nated, and all service instances assigned to that service unit are failed over; 
oth-
erwise, only the erroneous component is abruptly terminated, and all component
service instances that were assigned to it are failed over. Other components are
not terminated, but all service instances that contained one of the failed over
component service instances have their remaining component service instances
switched over
 
 
 * Below is the syslog on the node where SU1 is hosted.
 
 
 Oct 13 03:15:24 SYSTEST-PLD-1 osafamfnd[2725]: NO Assigning 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' QUIESCED to 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:24 SYSTEST-PLD-1 osafamfnd[2725]: NO Assigned 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' QUIESCED to 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:24 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Assigning 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' ACTIVE to 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO SU failover probation timer 
started (timeout: 1200000000000 ns)
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Performing failover of 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' (SU failover count: 1)
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO 
'safComp=COMP2,safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' faulted 
due to 'csiSetcallbackFailed' : Recovery is 'componentFailover'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State 
INSTANTIATED => TERMINATING
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Assigned 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' ACTIVE to 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removing 'all (4) SIs' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removing 
'safSi=TestApp_SI1,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removing 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removing 
'safSi=TestApp_SI3,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removing 
'safSi=TestApp_SI4,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 
'safSi=TestApp_SI1,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 
'safSi=TestApp_SI2,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 
'safSi=TestApp_SI3,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 
'safSi=TestApp_SI4,safApp=TestApp_TwoN' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO Removed 'all SIs' from 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 13 03:15:27 SYSTEST-PLD-1 osafamfnd[2725]: NO 
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State 
TERMINATING => 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.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to