Thank you for your help Morten, I am afraid we cannot use your solution in our project though.
I have party solved the issue by removing auto-down from the configuration and only allowing the cluster singleton to down members and members that notice quarantine when they reconnect will restart their actorsystems. However this causes a problem when the cluster singleton or acting master is the one who goes down or is separated from the cluster, now noone can down this node and no new singleton will start so the whole cluster is put in stasis. Anyone got any clever solution to this problem? Best Regards /Dennis Den onsdag 9 september 2015 kl. 09:29:53 UTC+2 skrev Dennis Jönsson: > > Hello! > > I am in the final stages of using Akka as our clustering solution, now I > have noticed that when one member of the cluster looses connection and > forms its own separate cluster it will not try to reconnect to the original > cluster when possible. > Is there something I need to do manually, perhaps listen to events and > trigger reconnection attempts? > > Also I have been trying to tinker with configuration to avoid quarantining > a member that looses connection to the cluster, is there a good way to > avoid this so that this member can reconnect at all without restarting the > remote actor system? > > Best Regards > > /Dennis > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
