> > The allocation strategy is used by the coordinator, a cluster singleton. > The currentShardAllocations will contain one entry for each registered > region actor (one per node). I think your currentShardAllocations only > contains one entry, i.e. both nodes have not registered when you send the > messages.
I see. So like you said, re-balancing would normally take care of this. Would implementing logic that waits for MemberUp notifications from all nodes in the cluster ensure that the region actors in those nodes have registered themselves with the coordinator? -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
