Hi Robert
Thanks a lot for sharing information..

Regarding notifications at high-rate..
I believe a more appropriate question would have been..  
are there "multiple" listener  for a single notification?
 
This is because, single-producer-single-consumer scenario can be implemented in 
many ways.. 
Notifications truly shine when there are multiple listener (many times unknown 
consumers) for a notification..
Based on your response, I believe BGP scenario is 
single-producer-single-consumer pattern (even with the new request).

With regards
Ashutosh

-----Original Message-----
From: Robert Varga [mailto:n...@hq.sk] 
Sent: Friday, October 07, 2016 1:52 PM
To: Ashutosh Bisht <ashutosh.bi...@ericsson.com>; 
mdsal-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org
Subject: Re: [mdsal-dev] Use of external datastore in ODL

On 10/07/2016 07:36 AM, Ashutosh Bisht wrote:
> Regarding BGP, I had two queries... 
> 1. Is the txn rate supported in a ODL-cluster enviroment?
> All our usecases require high availablility.. In particular the system needs 
> to be resilent against SPOF.
> In order to fulfill these requirements, we have decided to use ODL clustering 
> approach.

Not at this time, simply because of two things:
- CDS implementation falls over at those rates on AskTimeout
- memory consumption in replication goes up by a lot due to duplicate objects

The first one is BUG-5280, the second one is specific to BGP (which has other 
ways of replicating) and does not affect other plugins.

> 2. I am assuming the arrows (in peer -> AdjRIBIn -> EffRIBIn -> LocRib ) 
> denote the interactions (via datastore notifications). 
> If so, are these notifications used by some other ODL project / modules as 
> well or are they used solely within BGP project?

At this point the code resides inside one artifact, but the intermediate 
visibility is used by operators plus we do have an incoming feature request 
where an end user would modify the pipeline and plug in their own processing 
(i.e. use just the first stage and replace second and third stage by custom 
code).

Bye,
Robert

_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to