You can use ack. For example, the component that sends the message to you persistent actor will wait an acknowledge response. Your persistent actor will send this ack after sucessful persist the correspondent event. If the PA no send back response after a time, the component retry send the message. It leads to an at-leat-once-delivery behaviour and your persistent actor can receive unordered or duplicated messages.
Em quinta-feira, 5 de novembro de 2015 05:33:45 UTC-3, Anders Båtstrand escreveu: > > Dear group > > I am looking at Akka Persistence 2.4. > > Sometimes, we get write timeout against Cassandra, and we want to do a > retry. Using the new error handler system and BackoffSupervisor, the actor > is restartet as expected. However, I am not able to understand how I can > retry the message. > > In onPersistFailure i get the message i tried to persist. That I can not > use, since that is not the same message as was sent to the actor. I could > persist it again, perhaps, but them the callback with side-effects will not > be called. > > Do I have to do event sourcing, or is there some way of getting the > message (command) that was sent to the actor when it generated an event > that failed to persist? > > Best regards, > > Anders Båtstrand > -- >>>>>>>>>> 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.
