My understanding of resilience in a permanent actor in Akka is that it must have the same value in the reincarnations of the same actor in order to be able to restore state from a permanent repository. How will this work if the containing process is completely abandoned? Does this mean that the persistence of an actor with a known path should be maintained in some other specialized permanent storage?
I could understand how this will work with a specific player with a known path, but how will this work with a working actor who is controlled by a pool of routers?
Actors are created and stopped dynamically. How could I associate a long-lasting persistenceId with a specific player in the router pool and be able to restore the state of the actor in the event of a failure in the containing process.
cfcal source share