- **status**: review --> fixed
- **Comment**:
changeset: 6680:9761b6ed401c
tag: tip
parent: 6677:8f8719202335
user:Nagendra Kumar
date:Fri Jul 24 14:36:44 2015 +0530
summary: amfd: make ccb op and mw si swap mutually exclusive [#1105]
changeset: 6679:e22c9ac87
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 blo
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 --c
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 ac
The patch submitted for review
https://sourceforge.net/p/opensaf/mailman/message/34243280/
looks OK from a correctness point of view as I see it. But there are is an
incompleteness issue as I understand it. The ticket reports a problem for
both si-swap and failover. I dont see that the patch
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:** 4.5
dependency is unnecessary and an impediment to service availability.
/AndersBj
From: Nagendra Kumar [mailto:nagendr...@users.sf.net]
Sent: den 22 juni 2015 08:54
To: opensaf-tickets@lists.sourceforge.net
Subject: [tickets] [opensaf:tickets] #1105 AMFD: New standby crashes if blocked
on becoming
- **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
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: N
- **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:** ac
Here is what I go along:
1. Amf will return TRY_AGAIN for the SI-SWAP admin op when any ccb is going on.
And AMF will also set the "error string" appropriately.
2. AMF will return TRY_AGAIN in response of CCB, when SI-SWAP is in progress
and AMF will also set the "error string".
Also #1108 and #
- **status**: unassigned --> accepted
- **assigned_to**: Nagendra Kumar
- **Milestone**: future --> 4.5.2
---
** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier**
**Status:** accepted
**Milestone:** 4.5.2
**Created:** Wed Sep 17, 2014 06:18 PM UTC by Anders Bjornersted
- **Milestone**: 4.4.2 --> future
---
** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Sep 17, 2014 06:18 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Oct 07, 2014 08:09 AM UTC
**Owner:** nobody
- **Milestone**: 4.3.3 --> 4.4.2
---
** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier**
**Status:** unassigned
**Milestone:** 4.4.2
**Created:** Wed Sep 17, 2014 06:18 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Sep 18, 2014 08:02 AM UTC
**Owner:** nobody
Th
- **Comment**:
For the failover case, the new active AMFD really must wait eternally
on implementer-set, preferraby in combination with actions directed
at resolving the issue, such as the proposed admin-op on imm
(enhancement #1107).
The "alternative" of a cluster restart is not an alternative.
For the switchover case there is an alternative to "eternal wait" on
setting OI/applier. This is for the active AMFD to *reject* a switchover
if there is currently an active CCB modifying AMF data.
The AMFD must know if this is the case since it is the OI for that data.
---
** [tickets:#1105
Well, Amf as a HA provider can't wait eternal. Amf is doing some of imm
operation in a separate thread, but that is also not a suitable solution for
HA provider. As Amf has to deal with imm in each flow, Amf need not wait
eternal.
Even rebooting Standby SC is fine as it doesn;t harm HA.
Hence
---
** [tickets:#1105] AMFD: New standby crashes if blocked on becoming applier**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Wed Sep 17, 2014 06:18 PM UTC by Anders Bjornerstedt
**Last Updated:** Wed Sep 17, 2014 06:18 PM UTC
**Owner:** nobody
This ticket is in essence a continu
18 matches
Mail list logo
