The use case is I have a bunch of entities that are in an RDBMS and they are represented in memory by an actor per entity and those entities are spread across the cluster using ClusterSharding (assuming I can figure out why it wont start for me). However, on a per-node basis I would like to be able to send some messages to the shard region and have the shard region do special things. For example you could send ReportStatus to the region and then have them relay that to all the active actors they have, not just one. Or you could have a message saying Init(ids: List[int]) and have them initialize the actors with those ids so long as they are on this shard region. One thought I had was to subclass the Shard region and then adding my functionality to the receive. I am not sure, however, if this is even supported or if its a good idea. Also I am not sure if there is a better way to do this. It doesnt seem very specific to my problem scope so I am wondering if there is a better way to do this that I have missed. However, an essential feature to my system is that I need to 1) have some ways of knowing whether ids for an actor are local to this node so I am not sending a billion messages all over 2) Be able to lazy start the actor without having to send messages to all of a milion ids.
Any ideas are appreciated. -- >>>>>>>>>> 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.
