[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127338#comment-14127338
]
ASF GitHub Bot commented on STRATOS-779:
----------------------------------------
GitHub user R-Rajkumar opened a pull request:
https://github.com/apache/stratos/pull/28
Fixing STRATOS-779
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/R-Rajkumar/stratos master-agent
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/stratos/pull/28.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #28
----
commit fe5bcf0ae9da584fb7522375b73805547fd7157b
Author: R-Rajkumar <[email protected]>
Date: 2014-09-09T16:06:37Z
fixing cartridge instances exceeding max intance limit
----
> Stratos is creating more instances than the max limit
> -----------------------------------------------------
>
> Key: STRATOS-779
> URL: https://issues.apache.org/jira/browse/STRATOS-779
> Project: Stratos
> Issue Type: Bug
> Components: Autoscaler, Cartridge Agent, Cloud Controller
> Reporter: Rajkumar Rajaratnam
> Fix For: 4.1.0
>
>
> Currently, call from AS to CC to spawn new instances is synchronous. It has a
> timeout. Hence, there can be a situation like below,
> Call from AS to CC to spawn new instance can time out.
> Due to that, AS will not add the pending member for that call.
> But CC's attempt to spawn the instance can become successful with a very high
> delay (> time out)
> Meanwhile, the agent can send the instance activated event, even before CC
> sends the member started event. Since this member is not there in the
> topology, the event will get discarded. Hence, the member will never get
> activated in topology, and remains in created state. This is an additional
> member!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
