You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/09 18:00:12 UTC

[jira] [Resolved] (SLING-5286) re-activate fast topology change propagation

     [ https://issues.apache.org/jira/browse/SLING-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli resolved SLING-5286.
--------------------------------
    Resolution: Fixed

done in rev 1713478

> re-activate fast topology change propagation
> --------------------------------------------
>
>                 Key: SLING-5286
>                 URL: https://issues.apache.org/jira/browse/SLING-5286
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.2.0, Discovery Oak 1.0.2
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Impl 1.2.2, Discovery Oak 1.0.4
>
>
> With the discovery.base refactoring one functionality got lost: discovery.impl used to immediately ping the topology connectors upon any change in the local cluster. This speeds up change propagation 'from leafs to root' at least - while vice-versa this of course is impossible. This feature should be re-added.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)