You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by "Akila (JIRA)" <ji...@apache.org> on 2015/11/11 10:47:11 UTC

[jira] [Resolved] (STRATOS-1544) Topology Initialization Optimization

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

Akila resolved STRATOS-1544.
----------------------------
    Resolution: Fixed

Implemented in 60b801144dcb05e3664353c412bc1c3fffd7c55c

> Topology Initialization Optimization
> ------------------------------------
>
>                 Key: STRATOS-1544
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1544
>             Project: Stratos
>          Issue Type: Improvement
>          Components: Cloud Controller, Messaging
>    Affects Versions: 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4
>            Reporter: Imesh Gunaratne
>            Assignee: Akila
>             Fix For: 4.1.5
>
>
> Currently a Complete Topology event is sent every minute to let the subscribers to initialize the current state of the topology in their local instance. This causes the subscribers to wait for one minute (in the worst case) to start their standard functionality.
> May be we can improve this by sending the Complete Topology event on demand. The idea is to introduce a new topic called "initializer" to let the subscribers to request the Complete Topology event.



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