Hi, On Wed, Jun 8, 2016 at 5:05 PM, Akila Ravihansa Perera <[email protected]> wrote:
> Hi Manoj, > > How are those multiple managers going to sync artifacts between each other > using rsync? LB will route traffic only to 1st manager node and the 2nd > manager node as the fail-over, right? If all the managers try to push > artifacts to workers then there will be conflicts/overwrites. > > > I think the whole artifacts deployment/sync strategy is going to be > changed from C5 on-wards. AFAIU, we will not be publishing artifacts to > gateway nodes directly in C5. > AFAIU this is true for artifacts like webapps, etc. But IMHO an API is more of a configuration (similar to a load balancer rule which specifies how to forward the requests to the backend), so we would still need to publish/modify/delete APIs in the runtime. This is my take on APIs :) > Rather those artifacts will be injected at the Docker image build process. > So why don't we stick with SVN based DepSync for now (C4 products)? What is > the problem that we are trying to solve by moving to rsync that we > couldn't/cannot fix in SVN based model? > AFAIU the rsync based model is more fault tolerant and robust than the SVN based model for this particular purpose. However, the issue here is how rsync would handle concurrent modifications on the same file (the multiple manager node scenario). If we opt for the pull based rsync, this issue will be resolved, but there might an unnecessary load on the manager node with continuous polling. Or else we can use an improved pull based model, where a lightweight reliable notification is sent when an update is available, to notify the workers to pull the changes. > > Thanks. > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks and Regards, Isuru H. +94 716 358 048* <http://wso2.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
