The first scenario is reproduced with the changeset 7236.
App config : 2n red, 2 SUs with 4 COMPs , 1 sponsor with 3 dependent SIs, su
restart failover flag disabled.
Please find the amfd trace and application creation script.
Below are the steps followed.
* Ensure that all the SIs are assigned
* Lock the sponsor SI
* During the lock of sponsor SI operation, the component (COMP1 in SU2 )
hosting standby assignment doesn't respond to the CSI removal callback.
Attachments:
-
[1275_issue1.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/ae1313a5/5dea/attachment/1275_issue1.tgz)
(41.8 kB; application/x-compressed-tar)
---
** [tickets:#1275] AMF: SG is in unstable state ( standby csi removal timeout
during sponsor si lock )**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Thu Mar 19, 2015 01:48 PM UTC by Srikanth R
**Last Updated:** Mon Nov 02, 2015 09:23 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.------------------------------------------------------------------------------
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
