stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Imesh Gunaratne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STRATOS-614) Scale down logic does not execute as intended
Date Fri, 18 Apr 2014 09:31:16 GMT

    [ https://issues.apache.org/jira/browse/STRATOS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973918#comment-13973918
] 

Imesh Gunaratne commented on STRATOS-614:
-----------------------------------------

This issue was fixed by introducing dedicated message queues for each message receiver instance.
Changes were committed with commit revision: 06491aadae81b22699f57cfec007c4a4fa17295f

> 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)

Mime
View raw message