Hi Helena, First we must try to understand what is sending messages to the downed/removed nodes. After you have killed the B node the cluster failure detector will trigger and then I assume that you use some Cluster downing mechanism to remove the old B node from the cluster. Until that point it is expected that you will see these logs, because failure detector heartbeat messages will continue until the node is removed. After removal these log messages should stop, unless you continue to send something yourself.
Perhaps you can debug the messages with the settings described here: http://doc.akka.io/docs/akka/2.3.11/scala/logging.html#Auxiliary_remote_logging_options You are using Akka 2.3.11, right? Cheers, Patrik On Thu, May 14, 2015 at 10:21 PM, Helena Edelson < [email protected]> wrote: > Hi, > > I am looking for the right remoting config to tune for expected > unreachable behavior when a node goes down, to not continue past n-duration > to keep trying to connect. For what I'm doing it can be perfectly normal > for a node to go down and come up again. It's chaos monkey friendly. > > This is the known logging, that I want to prevent the cause of when > expected: I see it go on forever vs stop after a certain period: > WARN 19:50:12 Tried to associate with unreachable remote address > [akka.tcp://system@host:port]. Address is now gated for 1000 ms, all > messages to this address will be delivered to dead letters. Reason: > Connection refused: /host:port > > I have a cluster of 2 roles, say nodes of roles A and B. I have a node of > role A running, and as I bringing role B nodes up and down ( in lifecycle > testing), I want nodes of role A to not interpret the remoting 'Connection > refused' as an error but to simply stop attempting to use it, to forget > about the address/port completely. A downed node will come back with a new > port. So it's not the cluster MemberRemoved and Unreachable events, just > seems the remoting configuration I need to add/modify. > > What might that be? I've been trying a few things, nothing clicking yet ;) > > Thanks, > Helena > @helenaedelson > > > -- > >>>>>>>>>> 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. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> 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.
