Hi, everyone! We are currently building an application where resilience and recovery from errors is the absolutely most important requirement. Currently we are using Cassandra as persistent store, running in a cluster with multiple nodes. Still, we want to explore the possibility of being able to continue running our application even in the case all seed nodes are unavailable (application is already up and running). I realize that this may cause side-effects when letting end-users enter new data and believe these data have been persisted, but for parts of our actor hierarchy, it is better to be able to keep the actors running after a persistence failure occur.
I know how to handle the situation when persist calls fail, but when initializing new actors in a state of failed database, these new actors are left in the recovery state and will never start processing commands. This is due to the fact that even new actor instances always initializes in a state of recovery. Is there a way of overriding this behavious and forcing actor instances to transition into processCommands state? -- >>>>>>>>>> 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.
