Hi, *Context* : I have a hierarchy wherein a parent (few levels below root) is a persistent-actor (let us call this as partition-manager (this Id is ensured to be unique). It starts few child actors which are again persistent (let us call them as partition-handler-X where X is some unique number to ensure uniqueness of persistence-id). In addition to partition-handler-X, partition-manager also spawns few regular non-persistent actors
Above scheme works without any issues. *Problem* : Off late we encountered a situation wherein there are very sporadic journal-write failures (using LevelDB plugin). Write-failure may as well be triggered by an environment issue. While we are investigating the same, I also intend to have a level of protection at the actors' level to use Backoff supervision strategy *Clarification* : Is it advisable to use Backoff supervisor strategy for partition-manager (parent) as well as partition-handler-X (children) persistent-actors to cope with sporadic journal-write failures without disturbing any other actors of same hierarchy ? Regards Muthu -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.