I just posted a similar question. I want to know when a node is quarantined in code so we can auto-restart.
The node gets quarantined due to auto-down so you can bump up auto-down-unreachable-after or just disable it. If you're cluster is mainly static and you don't commonly add new nodes then disabling is probably fine. On Saturday, July 18, 2015 at 12:52:30 PM UTC-4, Eugene Dzhurinsky wrote: > > Yes, I've read that, and I think that I *may* face some network issues > now. I decreased the number of actors for each node to 5 with roundrobin > pool, and that seems to solve the problems - for the last night there's no > issue with the node marked as failed. > > The cluster is deployed on 7 nodes (3 Raspberry Pi 2 ARMv7 and 4 Raspberry > Pi B Armv6), so there definitely could be glitches in the network stack. > > To mitigate the problem when cluster gets 40% of its nodes down due to > some network error - is there any way to watch if the *current* node was > ditched off the cluster? Any event to listen on? > > I'd like to have an ability to restart the actor system on such event. My > nodes are totally stateless, so it doesn't harm to restart them as many > times as needed. > > Please advice. > > Thanks! > -- >>>>>>>>>> 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.
