Hi Regu, You can either use a group, in which case you are responsible for starting the routee on every node (note that you can also limit which nodes that have routees by means of the use-role configuration), or you can use a pool where the router will create routees on the cluster nodes.
With a group, when you add new nodes the routee on them will automagically become a part of the router destinations, so no need to communicate the change to the router - it is what it does. You can see examples of how to configure this in the docs here: http://doc.akka.io/docs/akka/2.4.6/scala/cluster-usage.html#Router_with_Group_of_Routees -- Johan Akka Team Typesafe - Reactive apps on the JVM Blog: letitcrash.com Twitter: @akkateam -- >>>>>>>>>> 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.
