- **Milestone**: future --> never
---
** [tickets:#380] SU Failover is being interpreted as Component Failover**
**Status:** duplicate
**Created:** Fri May 31, 2013 04:08 AM UTC by Nagendra Kumar
**Last Updated:** Wed Jul 10, 2013 06:51 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2390
Changeset: 3081
Setup: SLES 11 32bit VirtualBox?
Configuration: 2N SG with 2 SUs, each with 2 components and 1 SI with 2 CSIs
All the SUs and comps are in readiness state INSERVICE and the SI is fully
assigned.
SU1 is mapped on to SC-2 and SU2 is mapped on to SC-1
SU1 is active and SU2 is standby for the SI
Invoked ErrorReport? on the comp2 of SU1 with recommended recovery 3
(COMPONENT_FAILOVER)
As per the AMF specification, by default saAmfSUFailover configuration
attribute must be set to TRUE. (It shows <Empty> in immlist)
As per this configurations, SU Failover should be triggered which, as per spec
is explained as:
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 terminated, and all service instances assigned to that service unit
are failed over;
So, the following should be the sequence:
1. Cleanup script should be invoked for both the components of SU1
2. Active assignment should be set to components of SU2
3. If auto-repair is set, the SU should get reinstantiated and assigned Standby
for the SI
But the following are the things happened:
1. Cleanup script invoked for comp2 of SU1 (on which the error is reported) and
its CSI got failed-over
2. CSI assigned to comp1 of SU1 got switched-over i.e got quiesced and remove
callback for the CSI on comp1
3. SU2 got active assignment for the SI
4. SU1 restarted and got standby assignment for the SI
This behavior is as per the COMPONENT_FAILOVER recovery policy and when
saAmfSUFailover attribute is set to FALSE.
The following are the issues observed;
1. SU failover is being treated as component failover with both the default
configuration and also after setting saAmfSUFailover attribute to TRUE
2. Escalation to NODE_FAILOVER takes place in this case as the Component
Failover recovery is treated as SU Failover
The attached log file contains the output for two error report tries, one with
default configuration and the other with saAmfSUFailover attribute for SU1 set
to TRUE through immcfg.
---
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.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
