[
https://issues.apache.org/jira/browse/STRATOS-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185296#comment-14185296
]
Rajkumar Rajaratnam commented on STRATOS-911:
---------------------------------------------
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.
> VM and Container members should be able to have different expiry timeouts
> -------------------------------------------------------------------------
>
> Key: STRATOS-911
> URL: https://issues.apache.org/jira/browse/STRATOS-911
> Project: Stratos
> Issue Type: Improvement
> Components: Autoscaler
> Affects Versions: 4.1.0 M2
> Reporter: Rajkumar Rajaratnam
> Assignee: Rajkumar Rajaratnam
> Fix For: 4.1.0 M3
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
