[akka-user] Akka Singleton Cluster: Knowing when standby master has become primary

In a singleton cluster with 2 seed nodes, one of them is primary master and other one is standby, what notification should I subscribe to in the standby master that informs it that it has been moved to primary? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ

Re: [akka-user] Akka Cluster: Why Member does not have name property?

UTC-7, Patrik Nordwall wrote: > > No, MemberUp is a notification that a node/ActorSystem was added to the > cluster. > > You can read about ActorSystem here: > http://doc.akka.io/docs/akka/2.4.4/general/actor-systems.html > > /Patrik > > lör 16 apr. 2016 kl. 21:48 s

Re: [akka-user] Akka Cluster: Why Member does not have name property?

actor? On Saturday, April 16, 2016 at 11:22:02 AM UTC-7, Patrik Nordwall wrote: > > I think there is some misunderstanding. Member corresponds to an > ActorSystem, not an actor. > > /Patrik > > lör 16 apr. 2016 kl. 18:23 skrev Prasanna Thirumalai >: > >> When I

Re: [akka-user] Akka Cluster: Why Member does not have name property?

1:22:02 AM UTC-7, Patrik Nordwall wrote: > > I think there is some misunderstanding. Member corresponds to an > ActorSystem, not an actor. > > /Patrik > > lör 16 apr. 2016 kl. 18:23 skrev Prasanna Thirumalai >: > >> When I subscribe of cluster events, the 'Me

[akka-user] Akka Cluster: Why Member does not have name property?

When I subscribe of cluster events, the 'Member' entity does not have any name property where this property is same as given to the corresponding actor in system.actorOf. Because of this, there does not seem to be a way to get ActorSelection for a member on a MemberUp event. I get around it by

[akka-user] Akka Singleton Cluster: Inconsistent cluster behavior on worker restart

I am using Akka Cluster 2.4.3 and trying to setup a simple cluster in my machine to understand its working better. I have a singleton cluster with remoting enabled with primary and standby master and one worker node. Each of these 3 run in separate JVMs Things work fine when all the nodes are

[akka-user] Akka Singleton Cluster: resolveOnce of a worker by master fails after restart

down votefavorite I am using Akka Cluster 2.4.3 and trying to setup a simple cluster in my machine to understand its working better. I have a singleton cluster with r