You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Reka Thirunavukkarasu (JIRA)" <ji...@apache.org> on 2015/08/05 07:52:05 UTC

[jira] [Resolved] (STRATOS-1484) Spin a new member after the termination of existing member

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

Reka Thirunavukkarasu resolved STRATOS-1484.
--------------------------------------------
    Resolution: Done

This is added in c0e24c32beafbf0a57772ea110048a4d154b481a

> Spin a new member after the termination of existing member
> ----------------------------------------------------------
>
>                 Key: STRATOS-1484
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1484
>             Project: Stratos
>          Issue Type: Improvement
>          Components: Autoscaler
>    Affects Versions: 4.1.0
>            Reporter: Reka Thirunavukkarasu
>            Assignee: Reka Thirunavukkarasu
>             Fix For: 4.1.1
>
>
> In order to optimize the performance, stratos 4.1.0 supported member spinning in parallel to the member termination. But when having member min and max as 1 and when this particular member uses limited resources, it will not be possible to create a member in order to replace the existing one in the case of member faulty occurred. To avoid such situation, stratos has to wait for the proper termination of existing member before creating a new one. 
> This can be configured in autoscaler.xml as below:
>  <spinAfterTerminate>true</spinAfterTerminate>



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