With #1259 applied, SG does not remain in unstable state. But one problem still
remains,
after removal of assignments in active SU assignments of dependent SIs in
standby SUs are removed after making standby SU active. Since sponsor gets
completely unassigned, standby assignments for dependent should be removed
directly.
At the same time, as mentioned in the comment part of this ticket:
"Quiesced callbacks are sent for the dependent, which should not be as sponsor
SI is not in assigned state"
There is reported in similar ticket #292 which says:
#292 Unwanted quiescd callbacks for dependents are generated when sponsor fails
in the quiesced callback.
In bot the cases #292 component failover occurs during si lock phase but before
the completion of SI lock. Since SI lock is not completed and in between
comp-failover occurred, AMF can still give quiesced assignments to the
dependents also in the first part of recovery for comp-failover. After
completion of quiesced assignment or removal, in the second part of the
recovery ( which means give active to standby), AMF should not give active for
sponsor and dependents both, as sponsor is assigned.
With this analysis, postponing this ticket and #292 for the next release.
---
** [tickets:#1275] AMF: SG is in unstable state ( standby csi removal timeout
during sponsor si lock )**
**Status:** unassigned
**Milestone:** 4.7-Tentative
**Created:** Thu Mar 19, 2015 01:48 PM UTC by Srikanth R
**Last Updated:** Mon Mar 23, 2015 08:22 AM UTC
**Owner:** nobody
*Setup*
Version : 4.6 FC
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 is sponsor to SI2,3,&4.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=0(False)
component recovery policy - 3 (comp failover)
*Initial state*
All the AMF entities regarding the application are in unlocked states. SIs are
in fully assigned state.
*Issue* SG is in unstable state ( standby csi removal timeout during sponsor si
lock )
*Steps Performed*
-> Before performing lock operation of sponsor SI, ensured that component 1 in
SU2 ( the standby SU) does not respond in CSI removal callback.
-> SG went to unstable state, after the lock operation of sponsor SI.
Below are the logs on PL-4 ( where standby SU is hosted ) :
Mar 19 19:05:11 SYSTEST-PLD-2 osafamfnd[24560]: NO Removed
'safSi=SI1,safApp=test2nApp' from 'safSu=SU2,safSg=SG,safApp=test2nApp'
Mar 19 19:05:21 SYSTEST-PLD-2 osafamfnd[24560]: NO Removed
'safSi=SI2,safApp=test2nApp' from 'safSu=SU2,safSg=SG,safApp=test2nApp'
Mar 19 19:05:21 SYSTEST-PLD-2 osafamfnd[24560]: CR SU-SI record addition
failed, SU= safSu=SU2,safSg=SG,safApp=test2nApp : SI=safSi=SI3,safApp=test2nApp
Mar 19 19:05:21 SYSTEST-PLD-2 osafamfnd[24560]: CR SU-SI record addition
failed, SU= safSu=SU2,safSg=SG,safApp=test2nApp : SI=safSi=SI4,safApp=test2nApp
Below is the final state of SIs after the lock operation.
safSi=SI1,safApp=test2nApp
saAmfSIAdminState=LOCKED(2)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI2,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI3,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=SI4,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
---
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
