I solved my problem by using a third party service,that is ActiveMQ, to
check the Cluster's Integrity everytime a node is removed from the cluster
or everytime a node create/join a cluster rather than implementing a
downing strategy.
Thank you for your reply.
Best Regards,
Bourne.
.
On Friday,
please disregard my first question. I have that sorted out. Right now i'm
only concerned about the second case i mentioned where Terminated are not
received on both ends.
Thank you.
Best Regards,
Bourne.
On Thursday, February 5, 2015 at 7:01:02 PM UTC+7, Bourne Toulouss wrote:
>
Hi all,
I'm having a cluster system with many Master and many Slaves. I let Masters
watch over Slaves and Slaves watch over their Master. So that when a Master
is "terminated", corresponding slaves will re-register to a new Master and
deny all jobs until a master is found . Or when a slave is "
Hi all,
I have a question regarding the auto forming of clusters in akka.
At the moment , i have an app written in java, that consists of many actors
of the same role, using Cluster Singleton.
i use the automatic downing to handle the high availability aspect of the
application, so that when a no
Hi all,
At the moment, i have a java application with akka that uses master and
slave architecture.
masters and workers starts randomly.
I want it so if no master's been started yet, then worker will tryto join
the cluster with seed nodes as the nodes that the masters reside for a
number of time
