There are probably a few ways to do this. Most straight forward might be to start a local actor as part of each node's startup code. Then use Akka clustering to observe node failures. Use some deterministic strategy to reallocate that actor on some other host (let's say failed +1 in your ring). When the old node comes back up it starts its actor normally and then asks node current +1 to remove that actor from its AS.
Another way might be to use cluster sharding with a completely balanced distribution and rememberEntries = true. Akka would do more magic for you. This may not totally be what you want. This would guarantee 1 actor per server, however which actor was on which server wouldn't be deterministic. You might be able to provide some additional allocation strategy to Akka sharding that would give you additional control over placement, but that seems like a rabbit hole to me. Even if I could get it to work, I've worked too hard vs. option 1 and it may not be clear to the next developer what's going on. -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
