stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chamila De Alwis <>
Subject Re: [Discuss] Issue in Cartridge Agent Config Initialization Logic
Date Tue, 27 Jan 2015 19:59:10 GMT
Hi Imesh,

This was done to reflect the changes committed by Raj [1]. The
CompleteTopologyEvent is checked for consistency (member id being present
in the topology) and the initialized flag is set to true. Almost all the
time, the initialization goes through this path, because the
InstanceSpawnedEvent is missed by the agent. Is there a particular way this
breaks the member life cycle?

[1] -

Chamila de Alwis
Software Engineer | WSO2 | +94772207163

On Wed, Jan 28, 2015 at 12:00 AM, Imesh Gunaratne <> wrote:

> Hi Devs,
> I think there is an issue cartridge agent config initialization logic.
> Lakmal reported this while testing Kubernetes workflow. Cartridge agent
> wait until the Member Initialization event to send the Instance Started
> event, this is the intended behaviour:
> ​
> However Complete Topology event makes the above property True:
> ​As a result Member lifecycle breaks and member does not become active. I
> have now fixed this by removing the above highlighted line (in grey). Will
> build the php docker image and test this again.
> Thanks
> --
> Imesh Gunaratne
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos

View raw message