I haven't tried making snapshot yet, but I brain mimic the snapshot process and it seems there might be one problem there: what if a processor's memory state is so huge that it takes minutes to write to and read from disk? During the snapshot period some services might not be available. It will be great if we can somehow snapshot the memory state in memory first then dump the memory snapshot onto desk while keep the origin memory state updated by new events/commands.
I believe this is something common enough to be part of the persistence module in the future. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
