We're currently using akka for a variety of things, and are starting some experiments with akka-cluster, but we've hit one roadblock.
>From the documentation on akka-cluster membership lifecycle (http://doc.akka.io/docs/akka/2.5.4/scala/common/cluster.html#membership-lifecycle) : the actor system must be restarted before it can join the cluster again. The way we do deploys is to bootup new instances and bring them into the load balancer and move old instances out of the load balancer. It seems logical then, that anything in the load balancer should be a participant in our akka-cluster, while anything out of the load balancer should leave. The problem comes for how we do a rollback: we would bring the old instances back into the load balancer, but now they can't be part of the akka-cluster anymore. Restarting the process might work for some of our applications, but it's not an elegant solution in general for us, as some applications might have long-running jobs that should finish before a restart. Has anyone used akka-cluster in this type of deployment style, and what did you come up with? Thanks! -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
