You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/10/08 14:24:00 UTC
[jira] [Updated] (KARAF-5969) Refactoring of Cellar internals: use
level triggering instead of edge triggering
[ https://issues.apache.org/jira/browse/KARAF-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-5969:
----------------------------------------
Fix Version/s: (was: cellar-4.3.0)
> Refactoring of Cellar internals: use level triggering instead of edge triggering
> --------------------------------------------------------------------------------
>
> Key: KARAF-5969
> URL: https://issues.apache.org/jira/browse/KARAF-5969
> Project: Karaf
> Issue Type: Improvement
> Components: cellar
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> Generally speaking, the Cellar internals and logic are way too much complex.
> The main drawbacks are:
> 1. The cluster events (via the Hazelcast topic) contains all update data
> 2. The distributed maps are not really used (just to get the state)
> 3. Lot of Cellar components are useless from an user perspective (producers, handlers, ...)
> Instead, it would make more sense:
> 1. To store all in distributed maps
> 2. To have kind of distributed map listeners on node to "react" when a change is performed (instead of using the topic)
> 3. Remove the command/topic usage
> I will start a PoC around that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)