I know, that if I use a consistent hashing group router, it will always rout to the same registered routees.
So I wrote my application, with a few routees on there own routee-nodes and a public-node with a router, which is reachable by the client. If the client sends a message it is routed as it should be and it works fine. Now what I want to do is, add more public-nodes with thier own router that provides the same sending/routing behavior as every other public-node. What I mean is, that it should not matter if a client sends message XYZ to public-node A, B or C. It should always go to the same routee-node. At first I thought that akka may provides this behavior by default, because: 1. I used a group and not a pool router, so everyone knows the same routees 2. I leared that cluster nodes could be ordered So I assumed that the routees list is ordered and the different routers map the same keys to the same routees. But testing showed me that I was wrong. So, is there way in akka to achieve this behavior? Thanks. -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
