Hi, I saw this tweet by Patrik: 'Fantastic #Akka <https://twitter.com/hashtag/Akka?src=hash> contribution by Dominic Black merged to master. Cluster sharding remembers active entries. https:// github.com/akka/akka/pull/15597 … <https://t.co/P32NbQQokG>' I think it is a really cool feature to be able to reactivate active entities in a cluster when rebalancing occurs. So thanks to Dominic for the great work! I will benefit a lot from this feature. However I am wondering about fault tolerance.
One would typically use sharding when the actors doesn't fit on one machine (CPU or Memory) right? So restarting the sharded entries eagerly could end up in a software solution that will be unable to restart again, or will tear down the whole cluster when rebalancing. I guess we need some strategy to prevent this eager restarting when there are not enough (how do we now what is enough) nodes in the cluster. This will keep the cluster alive. How do the NoSQL Databases that support sharding do this? Is there already a strategy to prevent eager restarting to make this feature fault tolerant? Cheers, Jeroen -- >>>>>>>>>> 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.
