Uploaded image for project: 'Stratos'
  1. Stratos
  2. STRATOS-1660

Obsolete timeout calculation logic is buggy

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.1.4, 4.1.5
    • 4.1.5
    • Autoscaler
    • None

    Description

      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.

      Attachments

        Activity

          People

            ravihansa Akila Perera
            ravihansa Akila Perera
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment