Hello, I'm trying to figure out, how to handle journal failures with akka-persistence Views.
Imagine the following scenario: 1. Processor (actor system 1) writes messages 1-10 2. Processor (actor system 1) writes messages 11-20 3. View (actor system 2) reads messages 1-10 4. Journal crashes 5. <View: detect that journal is dead> - EVENT A 6. <View: detect that journal is back up> - EVENT B 7. <View: read messages 11-20 from the journal> - EVENT C 8. <View: resume normal operation> - back to normal processing The View is processing a slice of configuration that critically impacts the program's main request handling function. What I'm trying to achieve is to detect events: A, B and C, and wrap the programs logic around them, e.g. enqueue requests between events A and C, perform some kind of reload on event B. Is this possible with akka-persistence? If not, maybe at least detecting journal failure after a couple of polling attempts fail? Best regards, -- Jacek -- >>>>>>>>>> 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.
