- **status**: fixed --> accepted
- **Comment**:
Re-opening this enhancement ticket because the provided solution tended
to cause the PBE to attach as PBE-OI *before* the abort of non-critical
CCBs got executed in the cluster.
This because (a) the admin-operation was invoked asynchronously,
i.e. without waiting for reply; and (b) the actual abort of CCBs is
not generated not inside the admin-operation but by a background job
in the IMMND coord that runs once every second.
The result tended to be that the abort of non critical CCBs got executed
*after* PBE attached as OI and possibly even *after* the user that enabled
the PBE had got both an ok on the
PBE enabling CCB and allowed to start a new CCCB, had time to add
operations to the CCB, which then got aborted.
Relevant here is also problem/enhancement #744 to allow applications to
discriminate between ccb-abort due to resource problems and ccb-abort
due to validation error. In both cases the aborted ccb results in a
return code of SA_AIS_ERR_FAILED_OPERATION. This is necessary since that
is the only return code that according to SAF means that the CCB was
aborted.
LAcking a way to discriminate between resource-abort and validation-abort
one workarround is for some applications to *assume* that an abort
FAILED_OPERATION on a ccb call is due to resource problems; and to
retry the whole CCB from start at least once. If the abort was due to
resource problems then the second attempt may succeed. If the problem was
due to validation error then no new attempt will succeed.
---
** [tickets:#1261] IMM: Detach of PBE should abort all non-critical and
non-empty CCBs**
**Status:** accepted
**Milestone:** 4.7-Tentative
**Created:** Mon Mar 09, 2015 03:46 PM UTC by Anders Bjornerstedt
**Last Updated:** Fri May 22, 2015 11:38 AM UTC
**Owner:** Anders Bjornerstedt
This enhancement is related to defect ticket [#1260].
If the PBE detaches while there are any active non-critical and non-empty CCBs,
then such CCBs should be ABORTED, i.e. prevented from being further processed.
The abort must be done when the detach arrives over fevs. It must NOT be done
when the initial IMMND local PBE detach occurs, since that would make the ccb
state deviate locally.
In principle the abort is relevant for any main OI already involved in the CCB.
But this ticket will only deal with the departure of the PBE. Departure of
regular OIs will continue to be handled by OI timeout or by failure in the
apply/completed processing. One difference between the PBE and regular OIs is
that a regular OI can not attach as OI for a class/object if there are currently
active CCBs operating on the object or instances of the class.
---
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
