You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Imesh Gunaratne (JIRA)" <ji...@apache.org> on 2014/04/17 21:24:15 UTC

[jira] [Assigned] (STRATOS-614) Scale down logic does not execute as intended

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

Imesh Gunaratne reassigned STRATOS-614:
---------------------------------------

    Assignee: Imesh Gunaratne

> Scale down logic does not execute as intended
> ---------------------------------------------
>
>                 Key: STRATOS-614
>                 URL: https://issues.apache.org/jira/browse/STRATOS-614
>             Project: Stratos
>          Issue Type: Bug
>          Components: Eventing
>            Reporter: Imesh Gunaratne
>            Assignee: Imesh Gunaratne
>             Fix For: 4.0.0 RC1
>
>
> According to a flow test carried out on the latest code base, scale down functionality does not work as intended.
> Scenario: 
> 1. Partition Max Instance Count set to 3
> 2. Send a sample request load to take scale up action. Autoscaler will spin up 3 instances.
> 3. Stop the sample request load.
> 4. Let the service cluster scale down.
> 5. One instance being terminated but two remains.
> As found in the Autoscaler logs Member Stat Context of the terminated member is not being removed from the Cluster Context. As a result the same member being selected in each scale down action round.



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