Hi,
I will explain my approach as much as possible. The oldest node in the
hazelcast cluster is elected as the master node. In the failure of the
master node, next oldest node will be elected as the master node. This
master-slave configuration is just for deployment. When the hazelcast
cluster ele
HI Sathwik,
thanks for the reply i will do it .
Regards,
Tony
On Wed, May 27, 2015 at 12:36 PM, Sathwik B P wrote:
> Tony,
>
> Fork the project on your github and commit the changes to your fork.
>
> regards,
> sathwik
>
> On Wed, May 27, 2015 at 9:14 AM, tony pro wrote:
>
> > Hi Tammo,
> >
>
Tony,
Fork the project on your github and commit the changes to your fork.
regards,
sathwik
On Wed, May 27, 2015 at 9:14 AM, tony pro wrote:
> Hi Tammo,
>
> Thank you very much for the instructions it was very helpful.
> So, Now i have every thing working.
>
> For the forward work, we need to
Nandika,
I very well understand what you have put across, but it's secondary to me
now.
Sudharma,
My primary concern is to understand at a high level the deployment
architecture and how would master-slave configuration fit in. Are there any
restrictions imposed by the in-progress design?
Firstly
Hi Sathwik,
According to my understanding, in the clustering scenario, the master node
should perform all the deployment actions and the slave nodes also need to
perform some deployment actions. For example, the slave nodes also should
handle the process ACTIVATED event so that the process configu
Sudharma,
Where are you going to configure the master-slaves, is it in the web
application level or at the load balancer?
regards,
sathwik
On Tue, May 26, 2015 at 7:42 PM, sudharma subasinghe
wrote:
> Hi Tammo,
>
> Can you suggest the best method from these to implement? As first I
> suggested
