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

VM and Container members should be able to have different expiry timeouts

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.0 M2
    • Fix Version/s: 4.1.0 RC3
    • Component/s: Autoscaler
    • Labels:
      None

      Description

      VM and Container members should be able to have different values for expiry timeouts such as pending member expiry timeout and obsolete member expiry timeout

        Activity

        Hide
        raj@apache.org Rajkumar Rajaratnam added a comment -

        Fixed in c8bf4a874642bf9c8895ce124310218ce0f1347e

        Show
        raj@apache.org Rajkumar Rajaratnam added a comment - Fixed in c8bf4a874642bf9c8895ce124310218ce0f1347e
        Hide
        imesh Imesh Gunaratne added a comment -

        Raj: Can you please add details on your improvement?

        Show
        imesh Imesh Gunaratne added a comment - Raj: Can you please add details on your improvement?
        Hide
        raj@apache.org Rajkumar Rajaratnam added a comment -

        We have pending member expiry timeout and obsolete member timeout. These are configurable via autoscaler.xml.

        For VM case we used to have 15 min for pending member expiry timeout. But in container scenario, it should be less than 5 min. Because members are activated within 1 or 2 min.

        Earlier this timeout values can be configured globally, for all members, regardless of whether it is a container or vm.

        Now container & vm can have different values.

        Show
        raj@apache.org Rajkumar Rajaratnam added a comment - We have pending member expiry timeout and obsolete member timeout. These are configurable via autoscaler.xml. For VM case we used to have 15 min for pending member expiry timeout. But in container scenario, it should be less than 5 min. Because members are activated within 1 or 2 min. Earlier this timeout values can be configured globally, for all members, regardless of whether it is a container or vm. Now container & vm can have different values.

          People

          • Assignee:
            raj@apache.org Rajkumar Rajaratnam
            Reporter:
            raj@apache.org Rajkumar Rajaratnam
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development