Sorry for awakening this old thread... Is it really the case that there is all this fancy supervision architecture, and then a remote actor that has gone non-responsive, needs to be handled outside of the supervision hierarchy alltogether? was it considered enabling supervision to work such that the supervisor would know in case its remote child has gone unresponsive/gated/quarantined?
Perhaps I misinterpret the reference to the "cluster module" in the response by Dr. Roland Kuhn below. Thanks for clarifying, Matan On Thursday, January 31, 2013 at 10:13:26 PM UTC+2, rkuhn wrote: > > Hi Juan Pablo, > > 30 jan 2013 kl. 22:08 skrev Juan Pablo Vergara Villarraga: > > If a remote actor is not available due to power loss Can the supervision > strategy handle the situation? > > > No, loss of actors is managed by the Death Watch ( > http://doc.akka.io/docs/akka/2.1.0/general/supervision.html#What_Lifecycle_Monitoring_Means > > <http://www.google.com/url?q=http%3A%2F%2Fdoc.akka.io%2Fdocs%2Fakka%2F2.1.0%2Fgeneral%2Fsupervision.html%23What_Lifecycle_Monitoring_Means&sa=D&sntz=1&usg=AFQjCNFsY9OHlk2bVT8CIYRVEBaNRchLyA>), > > but support for detecting unreachable remote nodes is only present in the > cluster module. > > I have coded the example and I have shut down the remote actor system but > it seems that the supervision strategy only takes into account Exceptions > thrown by the remote actor once reached. > > > Yes, that is correct. > > I have already implemented the subscription to the events that indicates > that error in the connection have occurred. I still need to have access to > message the sender sent originally so the message do not get lost. > > > There is nothing you can subscribe to which tells you whether a given > message was processed on the remote system. If you cannot lose messages > then you need to persist them and use explicit acknowledgements from the > receiving actor to retire them from the local storage. You will also need > to implement resending and deduplication if you need exactly-once delivery; > you might want to read the documentation on message delivery guarantees: > http://doc.akka.io/docs/akka/2.1.0/general/message-delivery-guarantees.html > > Regards, > > Roland > > JP. > > -- > >>>>>>>>>> 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at http://groups.google.com/group/akka-user?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > *Dr. Roland Kuhn* > *Akka Tech Lead* > Typesafe <http://typesafe.com/> – Empowering professional developers to > build amazing apps. > twitter: @rolandkuhn <http://twitter.com/#!/rolandkuhn> > > -- >>>>>>>>>> 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.
