stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From david hbase <davidhb...@gmail.com>
Subject Re: [Discuss] [Issue] Sample Applications do not Activate
Date Mon, 09 Feb 2015 00:04:54 GMT
Hi,

The group-scaling-v1 can not be un-deployed,  after failed undeployed, can
not re-active again.

Also after this failed, the single-cartridge-app can not active.

David

On Sun, Feb 8, 2015 at 1:54 PM, Reka Thirunavukkarasu <reka@wso2.com> wrote:

> Hi
>
> After i have removed this particular check to start all adder and added
> Thread in order to start the monitor and adder as a workaround, i got the
> application active even with group scaling and application scaling. Please
> find the Topology as attached..So, i don't think, we have issues with the
> grouping logic in the case of group scaling.
>
> When i used executor service, the second monitor according to startup
> order always hangs and not executing properly. There seems to be some issue
> with the threading model that we are using. Can we look into that and fix
> it?
>
> Thanks,
> Reka
>
> On Sun, Feb 8, 2015 at 1:58 PM, Reka Thirunavukkarasu <reka@wso2.com>
> wrote:
>
>> According to my understanding, startup order is broken due to we start
>> all the adder at once..Could you please check on this?
>>
>> Thanks,
>> Reka
>>
>> On Sun, Feb 8, 2015 at 1:51 PM, Reka Thirunavukkarasu <reka@wso2.com>
>> wrote:
>>
>>> Hi Gayan,
>>>
>>> I found below segment has been added when starting the monitor adder.
>>> Could you please explain Why it has been added? We used to start the adder
>>> whenever needed as per earlier implementation by referring to dependency
>>> tree. Won't this break the dependency order of the Clusters? I found the
>>> problem for group scaling didn't happen due to the pendingMonitors list
>>> didn't get wiped out properly after the Monitor has been added. But
>>> couldn't figure out yet the actual root cause of it...
>>>
>>>
>>>  if (context.getApplicationChildContextList().size() > 0) {
>>>             for (ApplicationChildContext contextInner :
>>> context.getApplicationChildContextList()) {
>>>                 if
>>> (!this.aliasToActiveMonitorsMap.containsKey(contextInner.getId())) {
>>>                     pendingMonitorsList.add(context.getId());
>>>                     executorService.submit(new MonitorAdder(parent,
>>> contextInner, this.appId, instanceIds));
>>>                     if (log.isDebugEnabled()) {
>>>                         log.debug(String.format("Monitor Adder has been
>>> added: [cluster] %s ", contextInner.getId()));
>>>                     }
>>>                 }
>>>             }
>>>         }
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Sun, Feb 8, 2015 at 11:55 AM, Reka Thirunavukkarasu <reka@wso2.com>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> I have tested the group-scaling-v1. Application has become active.
>>>> After that instances tried to scaled up. In that only, there seems to be
>>>> some issue. I will check on that..Please find the attached topology view..
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>> On Sun, Feb 8, 2015 at 11:15 AM, Reka Thirunavukkarasu <reka@wso2.com>
>>>> wrote:
>>>>
>>>>> Thanks Imesh for fixing the issues..I will continue testing with the
>>>>> other samples..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Feb 8, 2015 at 10:59 AM, Imesh Gunaratne <imesh@apache.org>
>>>>> wrote:
>>>>>
>>>>>> May be this message processor is receiving an invalid message. Will
>>>>>> debug and see.
>>>>>>
>>>>>> On Sun, Feb 8, 2015 at 11:09 PM, Gayan Gunarathne <gayang@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Imesh,
>>>>>>>
>>>>>>> Seems "GroupStatusInactiveProcessor" is the last processor in
the
>>>>>>> "GroupStatusProcessorChain".We are printing the above warn message
if the
>>>>>>> next processor is null.
>>>>>>>
>>>>>>>        if (nextProcessor != null) {
>>>>>>>             // ask the next processor to take care of the message.
>>>>>>>             return nextProcessor.process(idOfComponent, appId,
>>>>>>> instanceId);
>>>>>>>         } else {
>>>>>>>
>>>>>>>             log.warn(String.format("No possible state change
found
>>>>>>> for [component] %s [instance]",
>>>>>>>                     idOfComponent, instanceId));
>>>>>>>         }
>>>>>>>
>>>>>>> Seems for the group-scaling sample is not fully activated.Only
one
>>>>>>> group(group2c3) is activated in that sample.I think we need to
check why
>>>>>>> the "GroupStatusInactiveProcessor" is triggered during the application
>>>>>>> deployment process.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gayan
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 8, 2015 at 9:53 PM, Imesh Gunaratne <imesh@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I tested both group-scaling and group-scaling-v1 applications
but
>>>>>>>> they did not activate:
>>>>>>>>
>>>>>>>> I can see the following warning in the log:
>>>>>>>>  WARN
>>>>>>>> {org.apache.stratos.autoscaler.status.processor.group.GroupStatusInactiveProcessor}
>>>>>>>> -  No possible state change found for [component] mygroup2
[instance]
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Sun, Feb 8, 2015 at 5:23 PM, Imesh Gunaratne <imesh@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Great work Reka! Thanks for looking into this!
>>>>>>>>>
>>>>>>>>> On Sun, Feb 8, 2015 at 3:27 AM, Reka Thirunavukkarasu
<
>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> I have fixed one issue that i found when using more
than one
>>>>>>>>>> groupInstances in the application. Now that, i could
get all the
>>>>>>>>>> single-group-* samples became active without any
issue.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Reka
>>>>>>>>>>
>>>>>>>>>> On Sat, Feb 7, 2015 at 12:08 PM, Reka Thirunavukkarasu
<
>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> Do we have the current state of the samples and
application
>>>>>>>>>>> state? When i tried group samples in mock and
it has become active..Did we
>>>>>>>>>>> fix this recently?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Reka
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Feb 7, 2015 at 11:54 AM, Reka Thirunavukkarasu
<
>>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Great job in organizing this samples..I just
tried the simple
>>>>>>>>>>>> sample. It saves lot of time in the testing
phase..
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Feb 6, 2015 at 7:08 PM, Imesh Gunaratne
<
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Chamila,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now we have a common set of artifacts
and deployment scripts
>>>>>>>>>>>>> for all the IaaSes except for deployment
policies. We have verified this
>>>>>>>>>>>>> with Mock IaaS.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Feb 6, 2015 at 11:47 PM, Chamila
De Alwis <
>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Is this on a particular one IaaS
or on mock IaaS?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Chamila de Alwis
>>>>>>>>>>>>>> Software Engineer | WSO2 | +94772207163
>>>>>>>>>>>>>> Blog: code.chamiladealwis.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Feb 6, 2015 at 9:18 PM, Imesh
Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks Dinithi, Manula and Vishanth
for contributing to fix
>>>>>>>>>>>>>>> sample applications! I'm now
looking into issues we have in grouping logic.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Feb 6, 2015 at 8:59 PM,
Dinithi De Silva <
>>>>>>>>>>>>>>> dinithis@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Both group-scaling and group-scaling-v1
also become
>>>>>>>>>>>>>>>> inactive after few seconds.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Feb 6, 2015 at 7:18
PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please find the current
state of the sample applications
>>>>>>>>>>>>>>>>> below:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> complex-appApplication
does not Activate
>>>>>>>>>>>>>>>>> complex-app-with-lbApplication
does not Activate
>>>>>>>>>>>>>>>>> dependent-scaling/sample-cartridgesApplication
Activates
>>>>>>>>>>>>>>>>> but becomes Inactive
after few seconds
>>>>>>>>>>>>>>>>> dependent-scaling/sample-groupsApplication
does not
>>>>>>>>>>>>>>>>> Activategroup-scalingApplication
does not Activate
>>>>>>>>>>>>>>>>> group-scaling-v1Application
does not Activate
>>>>>>>>>>>>>>>>> more-complex-appApplication
does not Activatenested-groupApplication
>>>>>>>>>>>>>>>>> does not Activatesingle-cartridgeApplication
Activates
>>>>>>>>>>>>>>>>> single-group-group-scalingApplication
does not Activate
>>>>>>>>>>>>>>>>> single-group-v1Application
does not Activate
>>>>>>>>>>>>>>>>> single-group-v2Application
does not Activate
>>>>>>>>>>>>>>>>> single-group-v3Application
does not Activate
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We need to investigate
each sample and fix the issues we
>>>>>>>>>>>>>>>>> have in application deployment
logic. Once a sample becomes working we can
>>>>>>>>>>>>>>>>> add that to the integration
test.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>> Committer & PMC Member,
Apache Stratos
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> *Dinithi De Silva*
>>>>>>>>>>>>>>>> Associate Software Engineer,
WSO2 Inc.
>>>>>>>>>>>>>>>> m:+94716667655 | e:dinithis@wso2.com
| w: www.wso2.com
>>>>>>>>>>>>>>>> | a: #20, Palm Grove, Colombo
03
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache
Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Gayan Gunarathne
>>>>>>> Technical Lead
>>>>>>> WSO2 Inc. (http://wso2.com)
>>>>>>> email  : gayang@wso2.com  | mobile : +94 766819985
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>

Mime
View raw message