[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-07-24 Thread Nagendra Kumar
- **status**: review -- fixed - **Comment**: changeset: 6680:9761b6ed401c tag: tip parent: 6677:8f8719202335 user:Nagendra Kumarnagendr...@oracle.com date:Fri Jul 24 14:36:44 2015 +0530 summary: amfd: make ccb op and mw si swap mutually exclusive [#1105]

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-07-22 Thread Minh Hon Chau
I have been testing the patch floated for review on default branch, it works fine in case of si-swap. Also, I'm trying to test in failover, below are steps I did: On SC-2 (standby): - immcfg -t 150 -m -a saAmfCtDefDisableRestart=0 safVersion=4.0.0,safCompType=OpenSafCompTypeIMMND - immcfg

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-07-22 Thread Nagendra Kumar
Hi Minh, The patch solves issues in case of switchover only as mentioned in the patch review description. In case of failover, it may not work(may be ccb are not related to Amf objects, so it may be working fine). Thanks -Nagu --- ** [tickets:#1105] AMFD: New standby crashes if

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-07-02 Thread Nagendra Kumar
Hi Anders, Thanks for your review. It is mentioned in the patch review that it doesn't handle fail-over case. But fail-over case could be sorted out if Imm returns the OI call immediately and marks Amfd as Implementer. As doing so is not going to give problem to Amf as it can

Re: [tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-06-29 Thread Anders Björnerstedt
For critical CCBs the wait can be indefinite since the delay can be due to problems on the file system. The AMF should not block a failover just because it can not attach as OI. There is no inherent functional dependence of the AMF failover mechanism on the AMF OI being available. Any such

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-06-29 Thread Nagendra Kumar
Hi Anders, Thanks for your comments. But imm need to take time-bound action in that case. It can't wait for a response for long. Thanks -Nagu --- ** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier - both failover and switchover** **Status:** review **Milestone:**

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-06-26 Thread Nagendra Kumar
- **status**: accepted -- review --- ** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier - both failover and switchover** **Status:** review **Milestone:** 4.5.2 **Created:** Wed Sep 17, 2014 06:18 PM UTC by Anders Bjornerstedt **Last Updated:** Mon Jun 22, 2015 06:53

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-06-22 Thread Nagendra Kumar
For non-critical ccb, ticket #1391 will take care. For critical ccb, Amf should ok to wait a little when PBE delays the response. So, I would be going ahead and implementing the two points mentioned above as part of #1105 and others will get closed. Thanks -Nagu --- ** [tickets:#1105] AMFD:

[tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked on becoming applier - both failover and switchover

2015-06-17 Thread Anders Bjornerstedt
- **summary**: AMFD: New standby crashes if blocked on becoming applier -- AMFD: New standby crashes if blocked on becoming applier - both failover and switchover --- ** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier - both failover and switchover** **Status:**