Hi Patrik, I think I forgot to mention a couple of things. The workers themselves are going to be pulling their work from RabbitMQ, they will persist it in case of failure, and then they will start processing it through its router. Since the workers themselves won't be receiving work in the form of messages, which would normally be used to start up an entry, I'm going to be having a singleton watchdog that periodically sends a "wakeup" message to each of the workers in case they get re-balanced and need to get started again.
Given this, could you clarify what you meant by using a few numbers for the message ids? Going off of the same example where I have 4 nodes and I need to have 40 shards, should the id values that the shardId() method produces fall within the same 40 id values? What about the values for the entryId() method? In terms of using the cluster Pub/Sub for the workers, do you mean having the stream publish the messages that it gets to a particular topic(s) and then have the workers subscribe to said topics and receive messages that way? Or did you have something else in mind for using Pub/Sub? -- >>>>>>>>>> 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.
