[
https://issues.apache.org/jira/browse/SLING-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-12378:
----------------------------------------
Fix Version/s: Content Distribution Journal Core 0.6.0
(was: Content Distribution Journal Core 0.5.0)
> Simplify handling of topology changes
> -------------------------------------
>
> Key: SLING-12378
> URL: https://issues.apache.org/jira/browse/SLING-12378
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Major
> Fix For: Content Distribution Journal Core 0.6.0
>
>
> Currently we have a complex system to build a Topology and notify on changes.
> * DiscoveryService receives Discovery message
> * DiscoveryService calls TopologyViewManager to update State of a subscriber
> (publish pod in k8s)
> * States are kept forever even if the subscriber dies
> Then every 5s we create a TopologyView which contains the alive subscribers
> (reported with TTL).
> Then we compute a diff between old and new topology view and call a listener
> with the diffs. At the end we set the new view as current view.
> I propose we remove view and diff and simply notify the listener when we
> receive a DiscoveryMessage. When asked for the current view we simply compute
> the view from the alive states.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
