[
https://issues.apache.org/jira/browse/STRATOS-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akila resolved STRATOS-1660.
----------------------------
Resolution: Fixed
Fix Version/s: 4.2.0
> 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
> Fix For: 4.2.0
>
>
> 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)
