Re: [akka-user] Trying to join member with wrong ActorSystem name, but was ignored, expected [X] but was [Y]

2014-04-08 Thread Carsten Saathoff
Hi, Am Montag, 7. April 2014 20:56:24 UTC+2 schrieb Eric Pederson: I'm probably going to move away from having the launcher join the cluster because there is a lot of log noise when the launcher app completes and leaves the cluster. Ideally you could subscribe to cluster events without

Re: [akka-user] Trying to join member with wrong ActorSystem name, but was ignored, expected [X] but was [Y]

2014-04-08 Thread Eric Pederson
Hi Carsten - yes. It didn't seem to do what I needed but I may experiment with it later. Actually joining the cluster worked exactly how I wanted it except for the noise in the logs after the launcher app quits after the cluster is fully launched. I ended up using just plain remoting and

Re: [akka-user] Trying to join member with wrong ActorSystem name, but was ignored, expected [X] but was [Y]

2014-04-07 Thread Konrad Malawski
Hello Eric, Is having the same actor system name required? Yes, for a cluster to converge the cluster members should have the same actorsystem-name. I like to think of it as: the ActorSystem being the “universe” in which Actors live, the cluster just allows them to live on different “planets”

Re: [akka-user] Trying to join member with wrong ActorSystem name, but was ignored, expected [X] but was [Y]

2014-04-07 Thread Eric Pederson
Thanks Konrad - I have an app that launches cluster members by ssh-ing into each box and running a script. The launcher app is joining the cluster to simplify the logic of knowing when everything is up. I had a different actor system name for the launcher because it's a different app. But it's