stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akila (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STRATOS-1660) Obsolete timeout calculation logic is buggy
Date Fri, 17 Jun 2016 08:30:05 GMT

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

Akila commented on STRATOS-1660:
--------------------------------

Fixed in f1e004517b2486d8e90ce6f4a7493beb5a2d0707

> Obsolete timeout calculation logic is buggy
> -------------------------------------------
>
>                 Key: STRATOS-1660
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1660
>             Project: Stratos
>          Issue Type: Bug
>          Components: Autoscaler
>    Affects Versions: 4.1.4, 4.1.5
>            Reporter: Akila
>            Assignee: Akila
>
> https://github.com/apache/stratos/blob/4.1.5/components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/context/partition/ClusterLevelPartitionContext.java#L750
> long obsoleteTime = System.currentTimeMillis() - obsoleteMember.getInitTime(); 
> The above does not take into account instances that were moved to the obsolete list while
in active status. In that case, it should be
> long obsoleteTime = System.currentTimeMillis() - obsoleteMember.getObsoleteInitTime();

> It should handle both inactive members (did not become active after being created), and
faulty members.



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

Mime
View raw message