I have an application where actors will normally be deployed remotely rather than locally. There will be one leader actor and the rest will be its junior.
Now the leader needs to know if the junior is alive or dead or not reachable. As to distinguish deadwith not reachable I have decided to have a convention that: If an actor is not reachable, it can be considered dead. (Is this assumption safe?) So now to know if a remote actor is dead or alive: One way is to keep polling repeatedly. Though I normally use context.watch for this purpose. Now the question is: How expensive is DeathWatch. What is the inner mechanism? As load-test would it be safe if I have an actor that is watching 100's of actors if not thousands? What would be the other ideal way to know if a remote actor is alive or dead? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
