- **summary**: IMM: Detach of OI or PBE should abort all non-critical and
non-empty CCBs --> IMM: Detach of PBE should abort all non-critical and
non-empty CCBs
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,26 +1,20 @@
This enhancement is related to defect ticket [#1260].
-If the PBE or any OI (not applier) detches while there are any active
-non-critical and non-empty CCBs, then such CCBs should be vetoed,
-i.e. prevented from being further processed. This is accomplished in the
-server by setting the mVeto member in such ccbs to an error code. In this
-case SA_AIS_ERR_NO_RESOURCES would be the correct choice.
+If the PBE detaches while there are any active non-critical and non-empty CCBs,
+then such CCBs should be vetoed, i.e. prevented from being further processed.
+This is accomplished in the server by setting the mVeto member in such ccbs
+to an error code. In this case SA_AIS_ERR_NO_RESOURCES would be the correct
+choice.
-Loss of PBE or involved OI should be regarded as a resource error and not as
-a validation error.
+Loss of PBE should be regarded as a resource error and not as a validation
error.
Such explicit vetoing must be done when the detach arrives over fevs. It must
-NOT be done when the initial IMMND local OI/PBE detach occurs, since that would
+NOT be done when the initial IMMND local PBE detach occurs, since that would
make the ccb state deviate locally.
-The veto is relevant for any main OI already involed in the CCB. It is relevant
-for the PBE because the PBE needs to receive all config changes. It is NOT
-relevant for appliers because appliers are just listeners who are no longer
listening. The 2PBE applier case should be verified/investigated that there are
-no issues if it detaches and re-attaches while a CCB is in progress, Such a
-ccb would get aborted in apply so it may be argued that it should be handled
-similarly. But we dont think the added compolexity for 2PBE is merited as an
-enhanced support for this rare case.
+In principle the veto 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.
-The veto will prevent the OmCcb user from wasting further operations/work on
this
-ccb, which is doomed to get aborted in CcbApply at the latest.
~~~~
---
** [tickets:#1261] IMM: Detach of PBE should abort all non-critical and
non-empty CCBs**
**Status:** accepted
**Milestone:** future
**Created:** Mon Mar 09, 2015 03:46 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu May 07, 2015 07:39 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 vetoed, i.e. prevented from being further processed.
This is accomplished in the server by setting the mVeto member in such ccbs
to an error code. In this case SA_AIS_ERR_NO_RESOURCES would be the correct
choice.
Loss of PBE should be regarded as a resource error and not as a validation
error.
Such explicit vetoing 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 veto 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.
---
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.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
