It might be also possible to use some sort of promotion algorithm, say, last in of a "role-X" takes over, the old know will see it and demote itself. All you need to do that is have one actor per node subscribed to cluster events, that;s how I do my promotion of active-passive nodes and it works like a charm. Also you need to agree in some sort of decentralized sorting criteria, for that I use current time in millis + node address to make sorting of nodes consistent among all other nodes.
That way they don't need to query anyone to know who is the current active node for an specific task. Hope that helps, Guido. On Tuesday, April 12, 2016 at 3:52:14 PM UTC+1, Paul Cleary wrote: > > Thanks, yea, guess it makes sense to have each member auto-down > themselves... > > "If my cluster doesn't reach quorum size, then stop me" >> >> -- >>>>>>>>>> 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.
