I get the idea. But does that mean I should create a top level actor like the /user guard but under user for all my actors and wait for the member to leave ? This is occurring inside of a Play Framework shutdown, so I would have to figure out how to orchestrate that.
On Monday, July 25, 2016 at 2:01:52 PM UTC-5, Konrad Malawski wrote: > > > Well the node leaving does nothing but shut down. The other nodes go on > with life of course. > > That's exactly the problem though: You exit the JVM before anyone has the > chance to even receive the Leave message. > > You should await the gossip message, basically: > > Cluster.subscribe(self, classOf[MemberRemoved]) > > ... case MembreRemoved(address) if address == selfAddress => System.exit() > > > Replied in a bit of a rush, hope you get the idea :-) > > You can also check out my Zen of Akka talk for a bit more wordy > explanation of this. > > -- > Konrad `ktoso` Malawski > Akka <http://akka.io> @ Lightbend <http://lightbend.com> > -- >>>>>>>>>> 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.
