Hi Anuruddha, I guess we have already fixed this issue sometimes back. I went though the log again and found that you haven't enabled Component startup synchronizer. If you enable it, it will ensure that CompleteTopologyEvent will be published only after SM is activated (SM will be activated only after AS).
In your logs, have a look at line number 402 : "Component startup synchronizer enabled: false" Please check whether your bin/stratos.sh have "-Dstratos.component.startup.synchronizer.enabled=true". If not, add it. Please let us know whether it resolves your issue. Thanks, Raj. On Mon, Aug 3, 2015 at 12:59 PM, Anuruddha Premalal <[email protected]> wrote: > Hi Raj, > > Thanks for the support given in finding the issue.I couldn't find a public > stratos jira for this so I've raised jira[1] to track this. > > [1] https://issues.apache.org/jira/browse/STRATOS-1487 > > > > On Mon, Aug 3, 2015 at 12:43 PM, Rajkumar Rajaratnam <[email protected]> > wrote: > >> Monitors were not created because CompleteTopologyEvent was published >> before AutoscalerComponent was activated. In the attached logs, >> >> Line number 478 - CompleteTopologyEvent was received by AS >> Line number 501 - AutoscalerComponent was activated >> >> When AS received CompleteTopologyEvent, it didn't load the application >> context from registry. Hence it just logged "The application is not yet >> deployed for this [application] asdevelopment" (Line number 482) and >> ignored the CompleteTopologyEvent. And CompleteTopologyEvent is published >> only once (until topology is initialized) - so there is no way that the >> monitors will be created. >> >> It needs to be fixed. >> >> Thanks, >> Raj. >> >> On Mon, Aug 3, 2015 at 12:06 PM, Anuruddha Premalal <[email protected]> >> wrote: >> >>> HI Raj, >>> >>> i'm attaching the carbon log file herewith. >>> >>> On Mon, Aug 3, 2015 at 11:52 AM, Rajkumar Rajaratnam <[email protected] >>> > wrote: >>> >>>> Hi Anuruddha, >>>> >>>> Cluster monitor can be created in two situations. >>>> >>>> 1) when a cluster is created for the first time (application deployment >>>> time) >>>> 2) when stratos is restarted >>>> >>>> If cluster monitor creation failed, it would log enough information >>>> about it (some error logs like "Monitor creation failed, even after >>>> retrying for 5 times") . You can trace back the logs and see the reason for >>>> it. I don't think scenario 1) is the reason for the above behaviour, >>>> because the members will not be created if the cluster monitor creation >>>> failed. Scenario 2) can be one reason for this behaviour. If it is the >>>> reason, then you should be able to see some error logs regarding cluster >>>> monitor creation failed. Have you restarted stratos? >>>> >>>> Further, "*A cluster monitor is not found in autoscaler context" *error >>>> doesn't necessarily mean that cluster monitor creation failed. It can >>>> be because cluster is undeployed and the monitor is removed before getting >>>> this event from CEP. >>>> >>>> If you could attach the complete log, we will be able to point out the >>>> issue. >>>> >>>> Thanks, >>>> Raj. >>>> >>>> On Mon, Aug 3, 2015 at 11:32 AM, Anuruddha Premalal <[email protected] >>>> > wrote: >>>> >>>>> Also this setup use kubernetes as the IaaS >>>>> >>>>> On Mon, Aug 3, 2015 at 11:31 AM, Anuruddha Premalal < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am working on $subject. >>>>>> >>>>>> In the current appfactory setup we have a single JVM Stratos 4.1.0 >>>>>> deployment. I am trying to get the autoscaling working since resetting >>>>>> the >>>>>> SM node each time of failure consumes time. Once a member fault event >>>>>> received to AS receives it but unable to continue with the following log. >>>>>> When will the cluster monitor get initiated? What would are the >>>>>> possibilities for failing the initialization of the cluster monitor? >>>>>> >>>>>> *INFO {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} >>>>>> - Faulty member detected [member-id] >>>>>> asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988 >>>>>> with [last time-stamp] 1438580270973 [time-out] 60000 milliseconds* >>>>>> *TID: [0] [SCC] [2015-08-03 11:26:38,956] INFO >>>>>> {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} - >>>>>> Publishing member fault event for [member-id] >>>>>> asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988* >>>>>> *TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG >>>>>> {org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver} >>>>>> - Member fault event received: [member] >>>>>> asdevelopment.anuasdevelopment.anuasdevelopment.domain38d5a847-d16a-4891-bbc0-6582cd9b9988 >>>>>> * >>>>>> *TID: [0] [SCC] [2015-08-03 11:26:38,969] DEBUG >>>>>> {org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver} >>>>>> - A cluster monitor is not found in autoscaler context [cluster] >>>>>> asdevelopment.anuasdevelopment.anuasdevelopment.domain* >>>>>> >>>>>> >>>>>> Thanks & Regards, >>>>>> -- >>>>>> *Anuruddha Premalal* >>>>>> Software Eng. | WSO2 Inc. >>>>>> Mobile : +94710461070 >>>>>> Web site : www.regilandvalley.com >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Anuruddha Premalal* >>>>> Software Eng. | WSO2 Inc. >>>>> Mobile : +94710461070 >>>>> Web site : www.regilandvalley.com >>>>> >>>>> >>>> >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Software Engineer, WSO2 >>>> >>>> Mobile : +94777568639 >>>> Blog : rajkumarr.com >>>> >>> >>> >>> >>> -- >>> *Anuruddha Premalal* >>> Software Eng. | WSO2 Inc. >>> Mobile : +94710461070 >>> Web site : www.regilandvalley.com >>> >>> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > *Anuruddha Premalal* > Software Eng. | WSO2 Inc. > Mobile : +94710461070 > Web site : www.regilandvalley.com > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
