stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Eppel (meppel)" <>
Subject RE: Testing stratos 4.1: termination behavior / STRATOS-1353
Date Fri, 01 May 2015 21:23:57 GMT
Hi Reka,

I re-run the scenario with debug logs turned on, dead lock detection, please find attached
artifacts, logs [] – for application see screenshot, artifacts
[1.]. If a terminate a member (c3) which has as termination behavior “terminate-dependents”
all dependents are properly terminated but not restarted .

Startup sequence is : c5 -> c4 -> G2 -> c3 -> c2 –> c1
Scenario : after all instances are active, terminate c3
termination of c2, c1 : ok
restart of c3 -> c2 -> c1: fail





From: Reka Thirunavukkarasu []
Sent: Friday, May 01, 2015 12:06 AM
To: dev
Subject: Re: Testing stratos 4.1: termination behavior / STRATOS-1353

Hi Martin,
Sorry that i couldn't get a chance to verify the scenarios that you mentioned with the code.
I will verify all other usecases for termination behavior and update with you on the progress..

On Fri, May 1, 2015 at 8:02 AM, Martin Eppel (meppel) <<>>
Hi Reka,

I merged in your fix for termination behavior and it fixes a couple of issues (terminate-all).
However, I encountered a couple of other potential issues:

1.      In the 2 level nested grouping scenario (as defined in STRATOS-1353) the terminate-none
seems to be incorrect (see application structure :
When I terminated the instance in G1 the instance c1 is terminated – but no new instance
is started.
See screen shot [1.], [2.] and artifacts attached (artifacts_scen_1)
After terminating c3 in G3 (bottom group, which has terminate-all defined) c3 and c2 start
up again but c1 still doesn’t come up (see log wso2carbon-full.log)

2.      In the 1 level grouping scenario (different application as in scen_1, see screen shot
[4.]) I terminate c3 in group G1. Group G1 defines as termination behavior “terminate-dependents”
and c1 depends on c2 and c2 depends on c3.
When I kill c1, c2 is correctly terminated but no restarted (instance terminated after: TID:
[0] [STRATOS] [2015-05-01 01:29:22,139])  . Instead I noticed exceptions in the log file (see
attached log file, below[3.])
Artifacts are attached (artifacts_scen_2)



[1.] Screenshot scenario 1


[2.] After terminating c1 :


[3.] Exceptions

        at org.apache.stratos.autoscaler.monitor.component.ParentComponentMonitor.allParentActive(
        at org.apache.stratos.autoscaler.monitor.component.ParentComponentMonitor.onChildTerminatedEvent(
        at org.apache.stratos.autoscaler.monitor.component.GroupMonitor.onTerminationOfInstance(
        at org.apache.stratos.autoscaler.monitor.component.GroupMonitor.onChildStatusEvent(
        at org.apache.stratos.autoscaler.monitor.cluster.ClusterMonitor.notifyParentMonitor(
        at org.apache.stratos.autoscaler.event.receiver.topology.AutoscalerTopologyEventReceiver$8.onEvent(
        at org.apache.stratos.messaging.listener.EventListener.update(
        at java.util.Observable.notifyObservers(
        at org.apache.stratos.messaging.event.EventObservable.notifyEventListeners(
        at org.apache.stratos.messaging.message.processor.topology.ClusterInstanceTerminatedProcessor.doProcess(
        at org.apache.stratos.messaging.message.processor.topology.ClusterInstanceTerminatedProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ClusterRemovedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ClusterInstanceInactivateProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ClusterInstanceActivatedProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ClusterCreatedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ApplicationClustersRemovedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ApplicationClustersCreatedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ServiceRemovedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.ServiceCreatedMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.topology.CompleteTopologyMessageProcessor.process(
        at org.apache.stratos.messaging.message.processor.MessageProcessorChain.process(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

[4.] Screen shot application


Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:,
Mobile: +94776442007

View raw message