Hey, folks. I'm doing some work to harden our cluster to unexpected failures, and I'm having trouble with an interaction between actor supervision and the cluster. We're using akka-cluster-2.3.4.
My cluster follows the worker dial-in example at http://doc.akka.io/docs/akka/2.3.14/scala/cluster-usage.html#Worker_Dial-in_Example. When my Frontend actor throws an exception, it's supervisor puts it through the restart process at http://doc.akka.io/docs/akka/2.3.14/general/supervision.html#What_Restarting_Means. A new Frontend instance is created and made active, but the Backend actors never get a new MemberUp message. Thus, they never re-register, and the Frontend's Seq of backend ActorRefs remains forever empty. Is there a pattern to get around this? I've tried a couple of things, but nothing's worked so far. For the moment, I'm just calling System.exit() in preRestart() and letting the keepalive script restart the master. I'm not proud of that. 8) Thanks, -H -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
