Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

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

Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

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,

Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

Well the node leaving does nothing but shut down. The other nodes go on with life of course. On Monday, July 25, 2016 at 1:34:37 PM UTC-5, Konrad Malawski wrote: > > What do you do after you call leave? > > -- > Konrad `ktoso` Malawski > Akka @ Lightbend

Re: [akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

What do you do after you call leave? -- Konrad `ktoso` Malawski Akka @ Lightbend On 25 July 2016 at 20:27:29, kraythe (kray...@gmail.com) wrote: In our code prior to shutting down a node we issue the following call. val cluster: Cluster =

[akka-user] [Cluster] Association failed even though cluster.leave(cluster.selfAddress) was called?

In our code prior to shutting down a node we issue the following call. val cluster: Cluster = Cluster.get(system) cluster.leave(cluster.selfAddress) However, despite that the other node still complains about unreachable node. Any way I can stop this? 2016-07-25 13:23:33 -0500 - [WARN] -