stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reka Thirunavukkarasu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (STRATOS-543) Topology needs to be sync when the member terminated
Date Thu, 20 Mar 2014 21:23:45 GMT

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

Reka Thirunavukkarasu updated STRATOS-543:
------------------------------------------

    Summary: Topology needs to be sync when the member terminated  (was: Topology needs to
be sync when we the member terminated)

> Topology needs to be sync when the member terminated
> ----------------------------------------------------
>
>                 Key: STRATOS-543
>                 URL: https://issues.apache.org/jira/browse/STRATOS-543
>             Project: Stratos
>          Issue Type: Bug
>          Components: Cloud Controller, Eventing
>    Affects Versions: 4.0.0 Alpha
>            Reporter: Reka Thirunavukkarasu
>             Fix For: 4.0.0 RC1
>
>
> Topology is not sync across nodes when a member terminated. This is because, CC is removing
the members from the Topology when a member got terminated, but in the TerminatedEvent, the
relevant processor is not removing the member from the Topology.
> If the decision to keep the member in the Topology even after member got Terminated,
unsubscription also needs to be fixed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message