Hi Tammo, The master node writes meta data. But runtime information must be available in all nodes.Since the folder is shared, all nodes will see the availability of a new process. My idea is for master node to write the meta data and other nodes to just read the meta data and load process.So we need a small delay between master node deployment and other nodes deployment.
Is there anyway to set the delay between master node and slaves until master node finish the deployment? Thank you Sudharma On 20 May 2015 at 13:01, Tammo van Lessen <tvanles...@gmail.com> wrote: > Hi Sathwik, > > On Wed, May 20, 2015 at 6:40 AM, Sathwik B P <sathwik...@gmail.com> wrote: > > > Sudharma/Tammo, > > > > 1) How do we plan to decide which is the master node in the cluster? > > > > I think the easiest approach is to always elect the oldest node in the > cluster to be the master. AFAIK Hazelcast can easily asked for this > information. > > > > > 2) Don't we need to stall the Deployment Pollers in the slave nodes? > > > > > Absolutely. > > Suggestion: > > I am not sure whether do we need Master-SLaves. Why not give every node > in > > the cluster the same status (Active-Active). > > > > When a new deployment is made, the load balancer can push it to any of > the > > available nodes. That node will probably acquire a distributed lock on > the > > deployment unit and acts as master for that deployment. This ensures > > optimum usage of the cluster nodes. Probably no static configuration of > > Master-Slave in the load balancer nor in the hazelcast. > > > > But this would not allow to have the hotdeployment via filesystem still > enabled, right? > > Best, > Tammo > > > -- > Tammo van Lessen - http://www.taval.de >
