https://issues.apache.org/jira/browse/STRATOS-1353
From: Reka Thirunavukkarasu [mailto:r...@wso2.com] Sent: Wednesday, April 29, 2015 11:55 AM To: dev Subject: Re: Testing Stratos 4.1 : nested grouping scenario with startup and termination issues (?) Hi Martin, While i was working on Application update, i fixed few issues with the termination behavior. Anyway there seems to be small issues in the logic which has to be fixed. I have started to verify this in my local setup. Can you create a jira? So that we can track it. I will update the progress in the jira.. Thanks, Reka On Tue, Apr 28, 2015 at 10:11 PM, Martin Eppel (meppel) <mep...@cisco.com<mailto:mep...@cisco.com>> wrote: Hi Reka, Thanks for following up - let me know if I should open a JIRA, Thanks Martin From: Reka Thirunavukkarasu [mailto:r...@wso2.com<mailto:r...@wso2.com>] Sent: Tuesday, April 28, 2015 5:37 AM To: dev Subject: Re: Testing Stratos 4.1 : nested grouping scenario with startup and termination issues (?) Hi Martin, Thanks for bringing this up. I have fixed some issue in the flow while testing application update support with instances count. I will go through your scenarios to reproduce it and update the thread with the progress.. Thanks, Reka On Tue, Apr 28, 2015 at 7:08 AM, Martin Eppel (meppel) <mep...@cisco.com<mailto:mep...@cisco.com>> wrote: I am testing a (nested grouping) scenario where a group defines a termination behavior “terminate-all”. When terminating the instance (of cartridge type c3), no new instance is restarted. My understanding is that a new instance should be started up. The scenario looks like this: Group ~G1 has a cartridge member c1 and group member ~G2 Group ~G2 has a cartridge member c2 and group member ~G3 Group ~G3 has a cartridge member c3 Startup dependencies are: c1 depends on G2, c2 depends on G3 ~G1 defines termination: none ~G2 defines termination: dependents ~G3 defines termination: all After startup, when all instances are active, instance c3 is terminated which correctly also terminates also instance c2 (since it depends on G3 / c3) . Issue 1: However, no new instances for c3 is started up (consequently no new instance for c2 should be started up as well) (see log see log wso2carbon.log) Only instance which remains running is c1. Issue 2: When subsequently c1 is manually being terminated, a new instance of c1 is started up (as opposed to Issue1) which I think is incorrect since it defines a startup dependency (c1 depends on G2) which is not fulfilled at the time (G2 should not be active since c2 is still terminated, see log wso2carbon-issue2.log, same log as wso2carbon.log but at a later time) WDYT ? Please find attached artifacts and logs Thanks Martin -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007<tel:%2B94776442007> -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
