---
** [tickets:#1535] imm: class and object applier set should be only on local
immnd**
**Status:** unassigned
**Milestone:** 5.0
**Created:** Fri Oct 09, 2015 01:44 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Oct 09, 2015 01:44 PM UTC
**Owner:** nobody
Information where applier is set (classes or objects) should be only stored on
the originating node where the applier is set.
Today, object and class applier set is done over fevs, and this information is
stored on all nodes. Newly synced node does not have information where the
applier is set.
Detaching the applier from the originating node and attaching to the new node
may have have different behavior then attaching the applier again to the
originating node or some veteran node.
This means that if the applier is set to a new object or class, it may get
different callbacks on veteran nodes (including the originating node) and new
nodes.
Appliers are only of interest on the local node. Where applier is set (object
or class) is not of interest for remote nodes.
Object/class applier set should be stored locally.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets