Hi Tal, thank you for you tip.
The answer to your question is: all the examples I've seen so far use one cluster only. You are right, the task itself does not even require the manager to be in any cluster if there is exactly one manager. So your answer is very reasonable. I'll soon check it out. However, the question that arises is: Is it necessary in Akka that all nodes of a cluster have the same code base? Thanks again, Klaus On Wednesday, February 15, 2017 at 12:03:44 PM UTC+1, Tal Pressman wrote: > > Hi, > > So here's a question - why do you want to have the manager and workers in > the same cluster? If they are, indeed, so decoupled that they should run on > separate machines, why not just have 2 separate clusters (or a cluster for > the workers, and a separate non-cluster process for the manager)? > > The manager can then communicate with the worker cluster using a > ClusterClient (http://doc.akka.io/docs/akka/2.4/scala/cluster-client.html) > without actually being part of the cluster. > > Tal > > > > -- >>>>>>>>>> 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.
