On Fri, May 24, 2013 at 9:53 PM, Amila Suriarachchi <am...@wso2.com> wrote:
> > > > On Thu, May 23, 2013 at 2:05 PM, Afkham Azeez <az...@wso2.com> wrote: > >> There is no guarantee that the cluster message will be reliably delivered >> to all members. For instance, due to a momentary network delay or delay in >> the node, other members may detect that a member has left, but in reality, >> that member may be still running. If a cluster message, such as a DepSync >> message is sent in such a scenario, the node will not receive that message, >> and may never update its deployment repo. >> >> We could implement one of the following solutions; >> 1. For selected cluster messages, we could replay them if a new member >> becomes available. We can't blindly replay all messages, but replaying the >> depsync message will cause no harm because the depsync operation is >> idempotent >> >> 2. For depsync, we can have periodic polling, but the polling interval >> should vary from about 1 minute to 5 minutes.r >> > How about changing polling interval according to the number of nodes in the cluster? For a basic example we can change the polling time t, 2t, 3t as cluster has 1 node, 2 nodes, 3 nodes etc.. If any node found a change in the repository, it send a cluster message. In this way it can be guaranteed that sync is happens in at least in O(n.t) time after a change in repo, where n=number of nodes in the cluster and t=polling time defined by user. Then this can be expanded by making more ordered/organized update by nodes. In that case the we can reduced that time to O(t). For depsynch problems there was a suggestion to implement svn polling at > workers. i.e worker periodically try to check out the code. is this an in > efficient method? > > thanks, > Amila. > >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: darsh...@wso2.com **Mobile: +94718566859 *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
