When scraping the router and using only sharding you will have to make sure that your MessageExtractor is implemented in a way that achieves desired load balancing.
Good point. Since the routees (and now the single workers) were going to be pulling data instead of getting data pushed to them, I was thinking of just having them get created randomly as needed based on the id values. In this case, since data isn't being pushed to the workers, it doesn't seem like Passivation would work in getting rid of the workers that weren't doing anything. I'm probably going to have to implement logic within the worker that just kills itself if it has been in an "idle" state for a period of time. > New entry with id 11 will be created in whatever shard > MessageExtractor.shardId(...) returned for that message. Oh so a shard can contain multiple instances of the same entry as long as their ids are different? Interesting. Anyways, I want to thank you Martynas and Patrik too for all of your great advice. Your guys' help has really been invaluable. Thank you! -- >>>>>>>>>> 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.
