[
https://issues.apache.org/jira/browse/STRATOS-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akila updated STRATOS-1544:
---------------------------
Affects Version/s: 4.0.0
4.1.3
4.1.4
Fix Version/s: 4.1.5
Description:
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.
was:
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 "topology-initializer" to let the
subscribers to request the Complete Topology event.
> Topology Initialization Optimization
> ------------------------------------
>
> Key: STRATOS-1544
> URL: https://issues.apache.org/jira/browse/STRATOS-1544
> Project: Stratos
> Issue Type: Improvement
> 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)
