[Changed subject] No, that’s not the point. I have event A that can be fired on nodeA, event B fired on node B, both are DTCNs but on different shard leaders. But I want both the events to be processed on same node.
Thanks, Faseela From: Tom Pantelis [mailto:tompante...@gmail.com] Sent: Friday, June 08, 2018 12:32 AM To: Faseela K <faseel...@ericsson.com> Cc: Michael Vorburger <vorbur...@redhat.com>; infrautils-...@lists.opendaylight.org; controller-dev <controller-dev@lists.opendaylight.org>; genius-...@lists.opendaylight.org; Robert Varga <n...@hq.sk> Subject: Re: [infrautils-dev] [controller-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ? On Thu, Jun 7, 2018 at 2:49 PM, Faseela K <faseel...@ericsson.com<mailto:faseel...@ericsson.com>> wrote: Tom, Currently we have certain cases, where we use EOS to ensure that we process a set of northbound+southbound events on same node. (I am not sure whether that is the actual purpose of EOS, but we use it like that as well. ;)) This has certain issues that in a 3 node cluster, your entity owner might be node2, but the datastores you are writing to as a result of the event has a leader on node1, and the writes will end up being slow. So if I have a mechanism to force default-operational shard DTCNs to be processed on the leader of default-config-shard(if my writes as a result of the notifications is going to be config shard writes), I would like to use that.(I am not sure whether I made it clear, we can discuss this in our next genius meeting as well. I can point you to some usages in genius.) Thanks, Faseela You can use a DataTreeChangeListener rather than a ClusteredDataTreeChangeListener. The former is only notified on the shard leader and thus only one in the cluster. From: Tom Pantelis [mailto:tompante...@gmail.com<mailto:tompante...@gmail.com>] Sent: Friday, June 08, 2018 12:13 AM To: Faseela K <faseel...@ericsson.com<mailto:faseel...@ericsson.com>> Cc: Michael Vorburger <vorbur...@redhat.com<mailto:vorbur...@redhat.com>>; infrautils-...@lists.opendaylight.org<mailto:infrautils-...@lists.opendaylight.org>; controller-dev <controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>>; genius-...@lists.opendaylight.org<mailto:genius-...@lists.opendaylight.org>; Robert Varga <n...@hq.sk<mailto:n...@hq.sk>> Subject: Re: [infrautils-dev] [controller-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ? On Thu, Jun 7, 2018 at 2:39 PM, Faseela K <faseel...@ericsson.com<mailto:faseel...@ericsson.com>> wrote: Not related in this context, but if we can get shard leader change notification, can we use that to derive an entity owner instead of using EOS? ;) Not exactly sure what you mean but shards and EOS are 2 different concepts...
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
