You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by "Akila (JIRA)" <ji...@apache.org> on 2016/06/14 09:43:01 UTC

[jira] [Created] (STRATOS-1660) Obsolete timeout calculation logic is buggy

Akila created STRATOS-1660:
------------------------------

             Summary: 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.5
            Reporter: 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)