You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Manula Chathurika Thantriwatte (JIRA)" <ji...@apache.org> on 2014/11/26 11:48:12 UTC

[jira] [Resolved] (STRATOS-1006) Lost of ReadyToShutDown event cause members who are in "ReadyToShutDown" forever

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

Manula Chathurika Thantriwatte resolved STRATOS-1006.
-----------------------------------------------------
    Resolution: Fixed

> Lost of ReadyToShutDown event cause members who are in "ReadyToShutDown" forever
> --------------------------------------------------------------------------------
>
>                 Key: STRATOS-1006
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1006
>             Project: Stratos
>          Issue Type: Bug
>          Components: Autoscaler
>    Affects Versions: 4.0.0
>            Reporter: Manula Chathurika Thantriwatte
>            Assignee: Manula Chathurika Thantriwatte
>             Fix For: 4.1.0 Alpha
>
>
> Proposed solution:
> AS delegate terminate flow will changes as following 
> 1 Put the member to the pending member termination list.(Remove the "sendMemberCleanupEvent" sending from the there) 
> 2. Implement a new drool to get the members from the pending member termination list and publish the instance clean up event.This will make sure to send instance clean up event all the members in the pending member termination list. 
> 3. Once cartridge agent receive that instance clean up, following things are happen as with the current implementation 
>   CA Publish member ready to shutdown event ---> CC publish member ready to shutdown event 
> 4. Once AS get the above member ready to shutdown event, it will move the member from pending member termination list to obsolete list 
> Terminate of the members from the obsolete list happen as the same with the current implementation. 



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