Hi all, I was thinking about the following scenario:
Suppose there's Job that's executed every now and again In the cluster, maybe a database cleanup, a message queue lookup, whatever... But you have a large cluster and you MUST have ONLY ONE node executing the job. I would be nice to let the cluster decide on it's own, which one of the nodes should run the job. Even better would be to let the cluster recognise that node that was executing the Job just crashed and there's no node doing the durty work and proactively promote a node for the task. There's lots of ways to implement this but I think that node roles fits very well with this problem. My question is, in order to promote a node and give it a new Role, do I have to "restar/reconect" the member? Or can it be updated at runtime? Thanks. -- >>>>>>>>>> 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.
