[
https://issues.apache.org/jira/browse/STRATOS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185512#comment-14185512
]
Udara Liyanage commented on STRATOS-915:
----------------------------------------
Hi,
There is a possibility that a activated cartridge instance get relaunched
when it is identified as a faulty member.
When cartridge agent running inside the instance fail to sends it's
statistics to CEP for 1min, Stratos marks the instance as a faulty members.
The the instance will be terminated and relaunch another instance in the
same partition.
Anyway should have a look to see the what causes the relaunch.
Touched, not typed. Erroneous words are a feature, not a typo.
> Vcloud: cartridge gets relaunched even though active
> ----------------------------------------------------
>
> Key: STRATOS-915
> URL: https://issues.apache.org/jira/browse/STRATOS-915
> Project: Stratos
> Issue Type: Bug
> Components: Cloud Controller
> Affects Versions: 4.0.0
> Environment: vcloud, stratos
> Reporter: Raghavendra Rangrej
> Attachments: wso2.log.tar.gz
>
>
> Hello,
> We are seeing an issue with stratos in vcloud.
> When we launch the cartridges we see that they become Active. After few hours
> the CLI shows they are active but we see that cartridge is tried to be
> getting relaunched.
> Issue here is, stratos CLI and other stratos components are out of sync.
> We expect a Active cartridge shouldn't be relaunched. .
> As the cartridges are configured with a a network of limited IP address, we
> see that next launch fail with no IP address available and it keeps on
> happenning launching 100s of vapps.
> Can you look in to this issue?
> It is blocking us in our orchestration testing.
> The wso2 log will be attached here with
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
