Tal, thanks for the response! As far as I know, when an actor is recovered through Akka Persistence - the whole set of events is being re-send to the actor, so it can recover the state. In my case, some states will have side-effects, like "send an e-mail" or "update the database". Obviously I don't want those events to be "replayed" by the new actor, I just need to - set the state data as it was seen when actor was "terminated" - set the timeouts (calculate the current time and recent state change time to set the appropriate timeout) - set the state to start from.
So I need not only record the state data and the current state, but also the time when that state was changed. Do I need to write some custom persistence model for that or I still can re-use Akka Persistence with some settings regarding the message replay policy? As for the number of threads my concern is: I have 10000 of actors, and all of them have certain timeouts. Once they recover the state after the actor system restart - there might be some bottleneck in processing of the new incoming messages from the external system (e.g to start a new actor that serves another workflow and init it's states) and process the timeout events. Thanks! -- >>>>>>>>>> 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.
