Your first step would probably be the documentation at : http://doc.akka.io/docs/akka/snapshot/scala/remoting.html
In particular the sections - "Lifecycle and Failure Recovery Model" You could also have a look at http://doc.akka.io/docs/akka/snapshot/general/configuration.html and any of the sections with keywords "gated,retry,quarantine" -b On Thursday, January 8, 2015 4:12:08 AM UTC-5, Matan Safriel wrote: > > Hi, > > I have read this other thread about the case of a remote being unavailable > <https://groups.google.com/forum/#!msg/akka-user/68TuTZLxqFI/3toNcO8yvMMJ>. > I assume it still applies to the most current version (?). > > My question is, how do both the supervision system (the part that's above > user code) and the death watch, in short, Akka, determine that a remote is > unavailable, and whether that is in any way configurable. I may assume some > polling is relied upon and wonder how exactly does it reach that > determination of "unavailability". > > In the same vein, I would like to ask whether actors perform any sort of > retry of their own, in case they determine that they *failed* *sending or > replying to *a message. Or is it the case that message sending is a "one > time attempt". Pointers to relevant source code are also welcome. > > Thanks in advance, > Matan > > *P.S. in case relevant changes are on the roadmap, it would be also cool > to know about it.* > -- >>>>>>>>>> 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.
