Hi all, I am writing an application using play and akka. I would like to understand a bit better how the cluster singleton and the router actually work.
I have multiple instances of the same play application running behind a load balancer (say 4 instances on 2 boxes). The application is simply manipulating json and using eventsourced to persist deltas. What I would like is to have a single write actor and a number (say 8) of read actors. I read about the cluster singleton and the router using remote actors. It seem to be what I want to use but I am trying to understand if this would actually work. When the first play app starts it creates the write actor and the router with 8 read actors. When the next one starts and joins the cluster, what is it going to happen? Reading the docs I understand the write actor is simply going to point back to the first instance write actor, is that correct? What if the second instance cannot join the cluster for a few seconds and the write actor gets created in the mean time? Will it still get changed to point to the write actor on the first instance after joining the cluster? What about the read actors? Will every instance try to create the read actors meaning that I will end up with 8 (reader pool size) x 4 (number of instances) read actors? Or maybe the cluster is smart enough to reconfigure itself when a new node joins or leaves the cluster? Thanks a lot for your help -- >>>>>>>>>> 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.
