You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Sajith Kariyawasam <sa...@wso2.com> on 2015/01/13 13:55:24 UTC
Issue in spawning instances in a complex application
Hi all,
Tried artifacts in [1], and seems there is an issue that cartridges outside
of the group are not starting up.
Looking into it now
[1]
https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
Thanks,
Sajith
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: Issue in spawning instances in a complex application
Posted by Gayan Gunarathne <ga...@wso2.com>.
I have added another fix for this one.(af4fa0093716bb6361205e0045c53b
de10480549)
Separate the if logic condition of startMonitor() in the
ParentComponentMonitor as we have noticed monitors will not start if the
child nodes are present.
Thanks,
Gayan
On Wed, Jan 14, 2015 at 10:13 AM, Sajith Kariyawasam <sa...@wso2.com>
wrote:
> @imesh, did you notice an issue in the startup order as well?
>
> On Wed, Jan 14, 2015 at 10:08 AM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> I'm looking into this issue
>>
>> On Wed, Jan 14, 2015 at 9:49 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Thanks Sajith, yes there seems to be a problem with the cartridge
>>> defined on the application level, all other clusters are getting activated:
>>>
>>>
>>>
>>>
>>> On Wed, Jan 14, 2015 at 9:18 AM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> I did another test with Gayan's fix, here are my observations. I have
>>>> attached the application json and the complete log too
>>>>
>>>> Application clusters are getting created
>>>> ==============================
>>>> Application Cluster group8tom.tomcat2.domain created in CC topology
>>>> Application Cluster group6tom.tomcat2.domain created in CC topology
>>>> Application Cluster group9tom.tomcat1.domain created in CC topology
>>>> Application Cluster group7tom.tomcat1.domain created in CC topology
>>>> Application Cluster mytomcat.tomcat.domain created in CC topology
>>>>
>>>> However, there is no instance spawn for cluster *mytomcat.tomcat.domain
>>>> *(Seems the cluster monitor has not created)
>>>>
>>>> Also, in the logs I can see the instance spawned up in following order,
>>>> group6tom, group7tom, group8tom, group9tom, but according to the startup
>>>> order defined, it should be group9tom, group8tom, group7tom,
>>>> group6tom, mytomcat, can someone verify this is the order that instances
>>>> should be spawned?
>>>>
>>>> [2015-01-14 08:55:29,187] INFO
>>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>>> spawn an instance via cloud controller: [cluster] group6tom.tomcat2.domain
>>>> [partition] P1 [network-partition-id] openstack_R1
>>>>
>>>> [2015-01-14 08:55:29,268] INFO
>>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>>> spawn an instance via cloud controller: [cluster] group7tom.tomcat1.domain
>>>> [partition] P1 [network-partition-id] openstack_R1
>>>>
>>>> [2015-01-14 08:55:29,318] INFO
>>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>>> spawn an instance via cloud controller: [cluster] group8tom.tomcat2.domain
>>>> [partition] P1 [network-partition-id] openstack_R1
>>>>
>>>> [2015-01-14 08:55:29,367] INFO
>>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>>> spawn an instance via cloud controller: [cluster] group9tom.tomcat1.domain
>>>> [partition] P1 [network-partition-id] openstack_R1
>>>>
>>>>
>>>>
>>>> On Tue, Jan 13, 2015 at 10:44 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Great work Gayan! Will verify this scenario.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Sajith,
>>>>>>
>>>>>> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066.
>>>>>> Please check this again with the latest code-base.
>>>>>>
>>>>>> Thanks,
>>>>>> Gayan
>>>>>>
>>>>>> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Seems Gayan has found the cause, and have fixed it. I will take an
>>>>>>> update and test..
>>>>>>>
>>>>>>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <
>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Tried artifacts in [1], and seems there is an issue that
>>>>>>>>> cartridges outside of the group are not starting up.
>>>>>>>>>
>>>>>>>>> Looking into it now
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sajith
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>
>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Sajith Kariyawasam*
>>>>>>>
>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: Issue in spawning instances in a complex application
Posted by Sajith Kariyawasam <sa...@wso2.com>.
@imesh, did you notice an issue in the startup order as well?
On Wed, Jan 14, 2015 at 10:08 AM, Sajith Kariyawasam <sa...@wso2.com>
wrote:
> I'm looking into this issue
>
> On Wed, Jan 14, 2015 at 9:49 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks Sajith, yes there seems to be a problem with the cartridge defined
>> on the application level, all other clusters are getting activated:
>>
>>
>>
>>
>> On Wed, Jan 14, 2015 at 9:18 AM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> I did another test with Gayan's fix, here are my observations. I have
>>> attached the application json and the complete log too
>>>
>>> Application clusters are getting created
>>> ==============================
>>> Application Cluster group8tom.tomcat2.domain created in CC topology
>>> Application Cluster group6tom.tomcat2.domain created in CC topology
>>> Application Cluster group9tom.tomcat1.domain created in CC topology
>>> Application Cluster group7tom.tomcat1.domain created in CC topology
>>> Application Cluster mytomcat.tomcat.domain created in CC topology
>>>
>>> However, there is no instance spawn for cluster *mytomcat.tomcat.domain
>>> *(Seems the cluster monitor has not created)
>>>
>>> Also, in the logs I can see the instance spawned up in following order,
>>> group6tom, group7tom, group8tom, group9tom, but according to the startup
>>> order defined, it should be group9tom, group8tom, group7tom, group6tom,
>>> mytomcat, can someone verify this is the order that instances should be
>>> spawned?
>>>
>>> [2015-01-14 08:55:29,187] INFO
>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>> spawn an instance via cloud controller: [cluster] group6tom.tomcat2.domain
>>> [partition] P1 [network-partition-id] openstack_R1
>>>
>>> [2015-01-14 08:55:29,268] INFO
>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>> spawn an instance via cloud controller: [cluster] group7tom.tomcat1.domain
>>> [partition] P1 [network-partition-id] openstack_R1
>>>
>>> [2015-01-14 08:55:29,318] INFO
>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>> spawn an instance via cloud controller: [cluster] group8tom.tomcat2.domain
>>> [partition] P1 [network-partition-id] openstack_R1
>>>
>>> [2015-01-14 08:55:29,367] INFO
>>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>>> spawn an instance via cloud controller: [cluster] group9tom.tomcat1.domain
>>> [partition] P1 [network-partition-id] openstack_R1
>>>
>>>
>>>
>>> On Tue, Jan 13, 2015 at 10:44 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great work Gayan! Will verify this scenario.
>>>>
>>>> Thanks
>>>>
>>>> On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Sajith,
>>>>>
>>>>> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066.
>>>>> Please check this again with the latest code-base.
>>>>>
>>>>> Thanks,
>>>>> Gayan
>>>>>
>>>>> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Seems Gayan has found the cause, and have fixed it. I will take an
>>>>>> update and test..
>>>>>>
>>>>>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sajith@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>>>>>>> outside of the group are not starting up.
>>>>>>>>
>>>>>>>> Looking into it now
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sajith
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>
>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Sajith Kariyawasam*
>>>>>>
>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: Issue in spawning instances in a complex application
Posted by Sajith Kariyawasam <sa...@wso2.com>.
I'm looking into this issue
On Wed, Jan 14, 2015 at 9:49 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks Sajith, yes there seems to be a problem with the cartridge defined
> on the application level, all other clusters are getting activated:
>
>
>
>
> On Wed, Jan 14, 2015 at 9:18 AM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> I did another test with Gayan's fix, here are my observations. I have
>> attached the application json and the complete log too
>>
>> Application clusters are getting created
>> ==============================
>> Application Cluster group8tom.tomcat2.domain created in CC topology
>> Application Cluster group6tom.tomcat2.domain created in CC topology
>> Application Cluster group9tom.tomcat1.domain created in CC topology
>> Application Cluster group7tom.tomcat1.domain created in CC topology
>> Application Cluster mytomcat.tomcat.domain created in CC topology
>>
>> However, there is no instance spawn for cluster *mytomcat.tomcat.domain *(Seems
>> the cluster monitor has not created)
>>
>> Also, in the logs I can see the instance spawned up in following order,
>> group6tom, group7tom, group8tom, group9tom, but according to the startup
>> order defined, it should be group9tom, group8tom, group7tom, group6tom,
>> mytomcat, can someone verify this is the order that instances should be
>> spawned?
>>
>> [2015-01-14 08:55:29,187] INFO
>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>> spawn an instance via cloud controller: [cluster] group6tom.tomcat2.domain
>> [partition] P1 [network-partition-id] openstack_R1
>>
>> [2015-01-14 08:55:29,268] INFO
>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>> spawn an instance via cloud controller: [cluster] group7tom.tomcat1.domain
>> [partition] P1 [network-partition-id] openstack_R1
>>
>> [2015-01-14 08:55:29,318] INFO
>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>> spawn an instance via cloud controller: [cluster] group8tom.tomcat2.domain
>> [partition] P1 [network-partition-id] openstack_R1
>>
>> [2015-01-14 08:55:29,367] INFO
>> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
>> spawn an instance via cloud controller: [cluster] group9tom.tomcat1.domain
>> [partition] P1 [network-partition-id] openstack_R1
>>
>>
>>
>> On Tue, Jan 13, 2015 at 10:44 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Great work Gayan! Will verify this scenario.
>>>
>>> Thanks
>>>
>>> On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>> Hi Sajith,
>>>>
>>>> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066.
>>>> Please check this again with the latest code-base.
>>>>
>>>> Thanks,
>>>> Gayan
>>>>
>>>> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>> wrote:
>>>>
>>>>> Seems Gayan has found the cause, and have fixed it. I will take an
>>>>> update and test..
>>>>>
>>>>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>>>>>> outside of the group are not starting up.
>>>>>>>
>>>>>>> Looking into it now
>>>>>>>
>>>>>>> [1]
>>>>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sajith
>>>>>>>
>>>>>>> --
>>>>>>> *Sajith Kariyawasam*
>>>>>>>
>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Sajith Kariyawasam*
>>>>>
>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> 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
>>>
>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: Issue in spawning instances in a complex application
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Sajith, yes there seems to be a problem with the cartridge defined
on the application level, all other clusters are getting activated:
On Wed, Jan 14, 2015 at 9:18 AM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> I did another test with Gayan's fix, here are my observations. I have
> attached the application json and the complete log too
>
> Application clusters are getting created
> ==============================
> Application Cluster group8tom.tomcat2.domain created in CC topology
> Application Cluster group6tom.tomcat2.domain created in CC topology
> Application Cluster group9tom.tomcat1.domain created in CC topology
> Application Cluster group7tom.tomcat1.domain created in CC topology
> Application Cluster mytomcat.tomcat.domain created in CC topology
>
> However, there is no instance spawn for cluster *mytomcat.tomcat.domain *(Seems
> the cluster monitor has not created)
>
> Also, in the logs I can see the instance spawned up in following order,
> group6tom, group7tom, group8tom, group9tom, but according to the startup
> order defined, it should be group9tom, group8tom, group7tom, group6tom,
> mytomcat, can someone verify this is the order that instances should be
> spawned?
>
> [2015-01-14 08:55:29,187] INFO
> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
> spawn an instance via cloud controller: [cluster] group6tom.tomcat2.domain
> [partition] P1 [network-partition-id] openstack_R1
>
> [2015-01-14 08:55:29,268] INFO
> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
> spawn an instance via cloud controller: [cluster] group7tom.tomcat1.domain
> [partition] P1 [network-partition-id] openstack_R1
>
> [2015-01-14 08:55:29,318] INFO
> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
> spawn an instance via cloud controller: [cluster] group8tom.tomcat2.domain
> [partition] P1 [network-partition-id] openstack_R1
>
> [2015-01-14 08:55:29,367] INFO
> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
> spawn an instance via cloud controller: [cluster] group9tom.tomcat1.domain
> [partition] P1 [network-partition-id] openstack_R1
>
>
>
> On Tue, Jan 13, 2015 at 10:44 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> Great work Gayan! Will verify this scenario.
>>
>> Thanks
>>
>> On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com>
>> wrote:
>>
>>> Hi Sajith,
>>>
>>> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066.
>>> Please check this again with the latest code-base.
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> Seems Gayan has found the cause, and have fixed it. I will take an
>>>> update and test..
>>>>
>>>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>>>>> outside of the group are not starting up.
>>>>>>
>>>>>> Looking into it now
>>>>>>
>>>>>> [1]
>>>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>>>
>>>>>> Thanks,
>>>>>> Sajith
>>>>>>
>>>>>> --
>>>>>> *Sajith Kariyawasam*
>>>>>>
>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> 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
>>
>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: Issue in spawning instances in a complex application
Posted by Sajith Kariyawasam <sa...@wso2.com>.
I did another test with Gayan's fix, here are my observations. I have
attached the application json and the complete log too
Application clusters are getting created
==============================
Application Cluster group8tom.tomcat2.domain created in CC topology
Application Cluster group6tom.tomcat2.domain created in CC topology
Application Cluster group9tom.tomcat1.domain created in CC topology
Application Cluster group7tom.tomcat1.domain created in CC topology
Application Cluster mytomcat.tomcat.domain created in CC topology
However, there is no instance spawn for cluster *mytomcat.tomcat.domain *(Seems
the cluster monitor has not created)
Also, in the logs I can see the instance spawned up in following order,
group6tom, group7tom, group8tom, group9tom, but according to the startup
order defined, it should be group9tom, group8tom, group7tom, group6tom,
mytomcat, can someone verify this is the order that instances should be
spawned?
[2015-01-14 08:55:29,187] INFO
{org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
spawn an instance via cloud controller: [cluster] group6tom.tomcat2.domain
[partition] P1 [network-partition-id] openstack_R1
[2015-01-14 08:55:29,268] INFO
{org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
spawn an instance via cloud controller: [cluster] group7tom.tomcat1.domain
[partition] P1 [network-partition-id] openstack_R1
[2015-01-14 08:55:29,318] INFO
{org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
spawn an instance via cloud controller: [cluster] group8tom.tomcat2.domain
[partition] P1 [network-partition-id] openstack_R1
[2015-01-14 08:55:29,367] INFO
{org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to
spawn an instance via cloud controller: [cluster] group9tom.tomcat1.domain
[partition] P1 [network-partition-id] openstack_R1
On Tue, Jan 13, 2015 at 10:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great work Gayan! Will verify this scenario.
>
> Thanks
>
> On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com>
> wrote:
>
>> Hi Sajith,
>>
>> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066.
>> Please check this again with the latest code-base.
>>
>> Thanks,
>> Gayan
>>
>> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> Seems Gayan has found the cause, and have fixed it. I will take an
>>> update and test..
>>>
>>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>>
>>>> Thanks
>>>>
>>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>>>> outside of the group are not starting up.
>>>>>
>>>>> Looking into it now
>>>>>
>>>>> [1]
>>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>>
>>>>> Thanks,
>>>>> Sajith
>>>>>
>>>>> --
>>>>> *Sajith Kariyawasam*
>>>>>
>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>>
>> 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
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: Issue in spawning instances in a complex application
Posted by Imesh Gunaratne <im...@apache.org>.
Great work Gayan! Will verify this scenario.
Thanks
On Tue, Jan 13, 2015 at 10:13 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
> Hi Sajith,
>
> Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066. Please
> check this again with the latest code-base.
>
> Thanks,
> Gayan
>
> On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> Seems Gayan has found the cause, and have fixed it. I will take an update
>> and test..
>>
>> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Thanks for reporting this Sajith! Will try to resolve this.
>>>
>>> Thanks
>>>
>>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>>> outside of the group are not starting up.
>>>>
>>>> Looking into it now
>>>>
>>>> [1]
>>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>>
>>>> Thanks,
>>>> Sajith
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
>
> 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
Re: Issue in spawning instances in a complex application
Posted by Gayan Gunarathne <ga...@wso2.com>.
Hi Sajith,
Yeah. AFAIR this also will be resolved with fixes for STRATOS-1066. Please
check this again with the latest code-base.
Thanks,
Gayan
On Tue, Jan 13, 2015 at 9:28 PM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> Seems Gayan has found the cause, and have fixed it. I will take an update
> and test..
>
> On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks for reporting this Sajith! Will try to resolve this.
>>
>> Thanks
>>
>> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Tried artifacts in [1], and seems there is an issue that cartridges
>>> outside of the group are not starting up.
>>>
>>> Looking into it now
>>>
>>> [1]
>>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>>
>>> Thanks,
>>> Sajith
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: Issue in spawning instances in a complex application
Posted by Sajith Kariyawasam <sa...@wso2.com>.
Seems Gayan has found the cause, and have fixed it. I will take an update
and test..
On Tue, Jan 13, 2015 at 7:19 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks for reporting this Sajith! Will try to resolve this.
>
> Thanks
>
> On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> Tried artifacts in [1], and seems there is an issue that cartridges
>> outside of the group are not starting up.
>>
>> Looking into it now
>>
>> [1]
>> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>>
>> Thanks,
>> Sajith
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: Issue in spawning instances in a complex application
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks for reporting this Sajith! Will try to resolve this.
Thanks
On Tue, Jan 13, 2015 at 6:25 PM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> Hi all,
>
> Tried artifacts in [1], and seems there is an issue that cartridges
> outside of the group are not starting up.
>
> Looking into it now
>
> [1]
> https://github.com/apache/stratos/tree/master/samples/complex-app/openstack/artifacts
>
> Thanks,
> Sajith
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos