subject:"Re\: \[Dev\] Latency in Deployment Synchronizer"

Re: [Dev] Latency in Deployment Synchronizer

2016-10-12 Thread Fathima Dilhasha



On Wed, Oct 12, 2016 at 11:53 AM, KasunG Gajasinghe  wrote:

>
>
> On Wed, Oct 12, 2016 at 10:51 AM, Fathima Dilhasha 
> wrote:
>
>> Hi All,
>>
>> I had a chat with KasunG and following are the facts I got to know which
>> explains the latency I was experiencing.
>>
>> 1. There is a scheduled task which is running in the DepSync enabled
>> manager nodes to commit new artifacts.
>> (The *DeploymentUpdateInterval* in carbon.xml defines how often the
>> task is run).
>>
>>  But this task is run only if the tenant is loaded at the specific
>> node.
>>  When there are new artifacts, the manager node sends a cluster
>> message to the other node indicating that there are new artifacts.
>>
>> 2. To compensate for any lost cluster messages there is a mandatory sync
>> mechanism run at each node irrespective of tenant loading.
>>  This task is run every 5-10 mins.
>>
>
> It is 5-15 mins by default. The max time is configurable. But, this won't
> run if the tenant is not loaded.
>

*Where can we configure the max time? *

>
>
>>
>> So, if tenant is not loaded at Node 1 and a file is changed at
>> "APIM/repository/tenants//..,
>> There is a latency of up to *15mins* until the changes are committed to
>> SVN.
>>
>> @KasunG, Please correct me if I've understood anything wrong.
>>
>>
> This is correct.
>
>
>> Thanks and Regards,
>> Dilhasha
>>
>>
>>
>> On Thu, Oct 6, 2016 at 10:15 AM, Fathima Dilhasha 
>> wrote:
>>
>>> Thanks Thilini. I will go through the webinar.
>>>
>>> On Thu, Oct 6, 2016 at 10:13 AM, Thilini Cooray 
>>> wrote:
>>>
 Hi Fathima,

 The delay in committing to svn can be caused by network latency.
 Have you specifically defined a checkout time period in your worker
 nodes?

 [1] is the webinar which clearly explains about the Dep-Sync mechanism.

 Hope it will give you an idea about the dep-sync behvior.

 [1] http://wso2.com/library/webinars/2012/10/enterprise-use-
 case-webinar-wso2-depsync-data-synchronization-between-nodes-cluster/

 Thanks.

 On Thu, Oct 6, 2016 at 10:02 AM, Fathima Dilhasha 
 wrote:

> I have a cluster with two nodes of WSO2 API Manager 1.10.0 with the
> following configurations for DeploymentSynchronizer.
> (Note that both the nodes are capable of committing.)
>
>  120
> 
>   
>   true
>   true
>   true
>  ...
>   
>
> I had the following observations when changing files at the path
> "APIM/repository/tenants//.."
>
> When I change a file within a folder in above path at 1 node,
> there is a latency of about 8mins until the change is committed to svn
> repo. (Note that update interval is only 2mins)
>
> I am not very clear about why there is a latency more than expected?
> Can this be due to added network latency?
>
> I would appreciate if you can point me to any documentation with
> details about the internals of depSync.
>
> I have referred to [1]
>
> [1] https://docs.wso2.com/display/CLUSTER420/Introduction+to
> +Deployment+Synchronizer
>
> Thanks & Regards,
> Dilhasha
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Best Regards,

 *Thilini Cooray*
 Software Engineer
 Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
 E-mail : thili...@wso2.com

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> Fathima Dilhasha
>>> *Software Engineer*
>>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>>> <%2B94%20%280%29%20773%20451194>
>>> dilha...@wso2.com 
>>>
>>
>>
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com 
>>
>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
> phone: +1 650-745-4499, 77 678 0813
>
>



-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Latency in Deployment Synchronizer

2016-10-12 Thread KasunG Gajasinghe

On Wed, Oct 12, 2016 at 10:51 AM, Fathima Dilhasha 
wrote:

> Hi All,
>
> I had a chat with KasunG and following are the facts I got to know which
> explains the latency I was experiencing.
>
> 1. There is a scheduled task which is running in the DepSync enabled
> manager nodes to commit new artifacts.
> (The *DeploymentUpdateInterval* in carbon.xml defines how often the
> task is run).
>
>  But this task is run only if the tenant is loaded at the specific
> node.
>  When there are new artifacts, the manager node sends a cluster
> message to the other node indicating that there are new artifacts.
>
> 2. To compensate for any lost cluster messages there is a mandatory sync
> mechanism run at each node irrespective of tenant loading.
>  This task is run every 5-10 mins.
>

It is 5-15 mins by default. The max time is configurable. But, this won't
run if the tenant is not loaded.


>
> So, if tenant is not loaded at Node 1 and a file is changed at
> "APIM/repository/tenants//..,
> There is a latency of up to *15mins* until the changes are committed to
> SVN.
>
> @KasunG, Please correct me if I've understood anything wrong.
>
>
This is correct.


> Thanks and Regards,
> Dilhasha
>
>
>
> On Thu, Oct 6, 2016 at 10:15 AM, Fathima Dilhasha 
> wrote:
>
>> Thanks Thilini. I will go through the webinar.
>>
>> On Thu, Oct 6, 2016 at 10:13 AM, Thilini Cooray 
>> wrote:
>>
>>> Hi Fathima,
>>>
>>> The delay in committing to svn can be caused by network latency.
>>> Have you specifically defined a checkout time period in your worker
>>> nodes?
>>>
>>> [1] is the webinar which clearly explains about the Dep-Sync mechanism.
>>>
>>> Hope it will give you an idea about the dep-sync behvior.
>>>
>>> [1] http://wso2.com/library/webinars/2012/10/enterprise-use-
>>> case-webinar-wso2-depsync-data-synchronization-between-nodes-cluster/
>>>
>>> Thanks.
>>>
>>> On Thu, Oct 6, 2016 at 10:02 AM, Fathima Dilhasha 
>>> wrote:
>>>
 I have a cluster with two nodes of WSO2 API Manager 1.10.0 with the
 following configurations for DeploymentSynchronizer.
 (Note that both the nodes are capable of committing.)

  120
 
   
   true
   true
   true
  ...
   

 I had the following observations when changing files at the path
 "APIM/repository/tenants//.."

 When I change a file within a folder in above path at 1 node,
 there is a latency of about 8mins until the change is committed to svn
 repo. (Note that update interval is only 2mins)

 I am not very clear about why there is a latency more than expected?
 Can this be due to added network latency?

 I would appreciate if you can point me to any documentation with
 details about the internals of depSync.

 I have referred to [1]

 [1] https://docs.wso2.com/display/CLUSTER420/Introduction+to
 +Deployment+Synchronizer

 Thanks & Regards,
 Dilhasha

 --
 Fathima Dilhasha
 *Software Engineer*
 Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
 <%2B94%20%280%29%20773%20451194>
 dilha...@wso2.com 

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> *Thilini Cooray*
>>> Software Engineer
>>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
>>> E-mail : thili...@wso2.com
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com 
>>
>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>



-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Latency in Deployment Synchronizer

2016-10-11 Thread Fathima Dilhasha

Hi All,

I had a chat with KasunG and following are the facts I got to know which
explains the latency I was experiencing.

1. There is a scheduled task which is running in the DepSync enabled
manager nodes to commit new artifacts.
(The *DeploymentUpdateInterval* in carbon.xml defines how often the
task is run).

 But this task is run only if the tenant is loaded at the specific node.
 When there are new artifacts, the manager node sends a cluster message
to the other node indicating that there are new artifacts.

2. To compensate for any lost cluster messages there is a mandatory sync
mechanism run at each node irrespective of tenant loading.
 This task is run every 5-10 mins.

So, if tenant is not loaded at Node 1 and a file is changed at
"APIM/repository/tenants//..,
There is a latency of up to *15mins* until the changes are committed to SVN.

@KasunG, Please correct me if I've understood anything wrong.

Thanks and Regards,
Dilhasha



On Thu, Oct 6, 2016 at 10:15 AM, Fathima Dilhasha  wrote:

> Thanks Thilini. I will go through the webinar.
>
> On Thu, Oct 6, 2016 at 10:13 AM, Thilini Cooray  wrote:
>
>> Hi Fathima,
>>
>> The delay in committing to svn can be caused by network latency.
>> Have you specifically defined a checkout time period in your worker nodes?
>>
>> [1] is the webinar which clearly explains about the Dep-Sync mechanism.
>>
>> Hope it will give you an idea about the dep-sync behvior.
>>
>> [1] http://wso2.com/library/webinars/2012/10/enterprise-use-
>> case-webinar-wso2-depsync-data-synchronization-between-nodes-cluster/
>>
>> Thanks.
>>
>> On Thu, Oct 6, 2016 at 10:02 AM, Fathima Dilhasha 
>> wrote:
>>
>>> I have a cluster with two nodes of WSO2 API Manager 1.10.0 with the
>>> following configurations for DeploymentSynchronizer.
>>> (Note that both the nodes are capable of committing.)
>>>
>>>  120
>>> 
>>>   
>>>   true
>>>   true
>>>   true
>>>  ...
>>>   
>>>
>>> I had the following observations when changing files at the path
>>> "APIM/repository/tenants//.."
>>>
>>> When I change a file within a folder in above path at 1 node,
>>> there is a latency of about 8mins until the change is committed to svn
>>> repo. (Note that update interval is only 2mins)
>>>
>>> I am not very clear about why there is a latency more than expected? Can
>>> this be due to added network latency?
>>>
>>> I would appreciate if you can point me to any documentation with details
>>> about the internals of depSync.
>>>
>>> I have referred to [1]
>>>
>>> [1] https://docs.wso2.com/display/CLUSTER420/Introduction+to
>>> +Deployment+Synchronizer
>>>
>>> Thanks & Regards,
>>> Dilhasha
>>>
>>> --
>>> Fathima Dilhasha
>>> *Software Engineer*
>>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>>> <%2B94%20%280%29%20773%20451194>
>>> dilha...@wso2.com 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>



-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Latency in Deployment Synchronizer

2016-10-05 Thread Fathima Dilhasha

Thanks Thilini. I will go through the webinar.

On Thu, Oct 6, 2016 at 10:13 AM, Thilini Cooray  wrote:

> Hi Fathima,
>
> The delay in committing to svn can be caused by network latency.
> Have you specifically defined a checkout time period in your worker nodes?
>
> [1] is the webinar which clearly explains about the Dep-Sync mechanism.
>
> Hope it will give you an idea about the dep-sync behvior.
>
> [1] http://wso2.com/library/webinars/2012/10/enterprise-
> use-case-webinar-wso2-depsync-data-synchronization-between-nodes-cluster/
>
> Thanks.
>
> On Thu, Oct 6, 2016 at 10:02 AM, Fathima Dilhasha 
> wrote:
>
>> I have a cluster with two nodes of WSO2 API Manager 1.10.0 with the
>> following configurations for DeploymentSynchronizer.
>> (Note that both the nodes are capable of committing.)
>>
>>  120
>> 
>>   
>>   true
>>   true
>>   true
>>  ...
>>   
>>
>> I had the following observations when changing files at the path
>> "APIM/repository/tenants//.."
>>
>> When I change a file within a folder in above path at 1 node,
>> there is a latency of about 8mins until the change is committed to svn
>> repo. (Note that update interval is only 2mins)
>>
>> I am not very clear about why there is a latency more than expected? Can
>> this be due to added network latency?
>>
>> I would appreciate if you can point me to any documentation with details
>> about the internals of depSync.
>>
>> I have referred to [1]
>>
>> [1] https://docs.wso2.com/display/CLUSTER420/Introduction+
>> to+Deployment+Synchronizer
>>
>> Thanks & Regards,
>> Dilhasha
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Latency in Deployment Synchronizer

2016-10-05 Thread Thilini Cooray

Hi Fathima,

The delay in committing to svn can be caused by network latency.
Have you specifically defined a checkout time period in your worker nodes?

[1] is the webinar which clearly explains about the Dep-Sync mechanism.

Hope it will give you an idea about the dep-sync behvior.

[1]
http://wso2.com/library/webinars/2012/10/enterprise-use-case-webinar-wso2-depsync-data-synchronization-between-nodes-cluster/

Thanks.

On Thu, Oct 6, 2016 at 10:02 AM, Fathima Dilhasha  wrote:

> I have a cluster with two nodes of WSO2 API Manager 1.10.0 with the
> following configurations for DeploymentSynchronizer.
> (Note that both the nodes are capable of committing.)
>
>  120
> 
>   
>   true
>   true
>   true
>  ...
>   
>
> I had the following observations when changing files at the path
> "APIM/repository/tenants//.."
>
> When I change a file within a folder in above path at 1 node,
> there is a latency of about 8mins until the change is committed to svn
> repo. (Note that update interval is only 2mins)
>
> I am not very clear about why there is a latency more than expected? Can
> this be due to added network latency?
>
> I would appreciate if you can point me to any documentation with details
> about the internals of depSync.
>
> I have referred to [1]
>
> [1] https://docs.wso2.com/display/CLUSTER420/Introduction+to+Deployment+
> Synchronizer
>
> Thanks & Regards,
> Dilhasha
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Latency in Deployment Synchronizer

Re: [Dev] Latency in Deployment Synchronizer

Re: [Dev] Latency in Deployment Synchronizer

Re: [Dev] Latency in Deployment Synchronizer

Re: [Dev] Latency in Deployment Synchronizer

5 matches

Site Navigation

Mail list logo

Footer information