[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam updated STRATOS-779:
----------------------------------------
Description:
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!
> 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)
