We experienced similar problem many times and gave up on using persistence mode in shard coordinator - "ddata" works for us much better. Even when failure happens, which ususally occures during rolling-restart, it is way easier to recover - no need to tamper with persistent storage. So if you don't need to recreate entities on the same nodes this might be a better approach. Unfortunately there is no built-in resilience in akka for such type of exception - no way to have SupervisorStrategy for shard coordinator. We step-aside this problem by external monitoring of a service that depends on cluster sharding.
-- >>>>>>>>>> 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.
