Re: [Dev] Latency in Deployment Synchronizer

​ 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

Re: [Dev] Latency in Deployment Synchronizer

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

Re: [Dev] Latency in Deployment Synchronizer

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

Re: [Dev] Latency in Deployment Synchronizer

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

Re: [Dev] Latency in Deployment Synchronizer

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]

[Dev] Latency in Deployment Synchronizer

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