Menu

#1107 IMM: Provide an admin-operation for aborting all non-critical CCBs

4.7.FC
fixed
None
enhancement
imm
nd
4.7
major
2015-09-15
2014-09-18
No

This is related to ticket #1105:

http://sourceforge.net/p/opensaf/tickets/1105/

The AMF needs to be able to force the immsv to abort all non critical CCBs
in certain situations. The prime example is an si-swap or failover where
there is an on going (non critical) CCB that has modified AMF data.

The new active (and the new standby applier) can not attach as OIs
as long as there is an open CCB operating on the data that the OI/applier
is registered/registering to monitor.

This new admin-operation can be used either automatically by the AMF,
or manually by the operator.

The autmatic use by the AMF will be a separate enhancement dependent on
this one.

Related

Tickets: #1107
Wiki: NEWS-4.7.0

Discussion

  • Anders Bjornerstedt

    • Milestone: 4.6.FC --> future
     
  • Anders Bjornerstedt

    This enahcnement can be used bot has a basis for solving the AMF problem
    descibed in #1105 and also as a starting point for #1261.

     
  • Anders Bjornerstedt

    • status: unassigned --> accepted
    • assigned_to: Anders Bjornerstedt
    • Version: 4.6 --> 4.7
    • Milestone: future --> 4.7-Tentative
     
  • Anders Bjornerstedt

    • status: accepted --> review
     
  • Anders Bjornerstedt

    • status: review --> fixed
     
  • Anders Bjornerstedt

    changeset: 6547:75428dda66d5
    tag: tip
    user: Anders Bjornerstedt anders.bjornerstedt@ericsson.com
    date: Fri May 08 16:16:38 2015 +0200
    summary: IMM: Support admin-op for aborting non critical ccbs [#1107]

     

    Related

    Tickets: #1107

  • Anders Bjornerstedt

    • status: fixed --> accepted
     
  • Anders Bjornerstedt

    Need to re-open this enhancement because it fails to abort non-critical
    CCBs that are "idle" i.e. not currently waiting on reply from any OI.
    For example, the CCB may have processed a number of create/delete/modify
    ops and receiver reply from OI, but then the ccb-om-client goes idle
    for some time. Such a ccb is not waiting on any reply from any OI yet
    is non-epmpty and not being committed or aborted yet.

     
  • Anders Bjornerstedt

    • status: accepted --> review
     
  • Anders Bjornerstedt

    Review of second patch (correction patch).

     
  • Anders Bjornerstedt

    • status: review --> fixed
     
  • Anders Bjornerstedt

    changeset: 6565:a2d0bc92571d
    tag: tip
    user: Anders Bjornerstedt anders.bjornerstedt@ericsson.com
    date: Wed May 20 23:48:21 2015 +0200
    summary: IMM: Correction to support for admin-op for aborting non critical ccbs [#1107]

     

    Related

    Tickets: #1107

  • Zoran Milinkovic

    • status: fixed --> accepted
    • assigned_to: Anders Bjornerstedt --> Zoran Milinkovic
     
  • Zoran Milinkovic

    When CCB operation is done immediately after OpenSAF started, CCB operation failes.
    The easiest way to produce the problem is to run immcfg command just after OpenSAF srarts.

     
  • Zoran Milinkovic

    • status: accepted --> review
     
  • Zoran Milinkovic

    default(4.7):

    changeset: 6827:5ac4e09c8618
    tag: tip
    user: Zoran Milinkovic zoran.milinkovic@ericsson.com
    date: Fri Aug 14 11:17:10 2015 +0200
    summary: imm: force cleanTheHouse job on aborting non-critical CCB admin op [#1107]

     

    Related

    Tickets: #1107

  • Zoran Milinkovic

    • status: review --> fixed
     

Log in to post a comment.