Confirmed, please create a ticket<http://doc.akka.io/docs/akka/current/project/issue-tracking.html> . The regression is in 11c8379 Thanks for reporting. I'm sure this will be given high priority. /Patrik
On Sat, Mar 29, 2014 at 4:05 AM, Brian Dunlap <[email protected]> wrote: > Hi guys, > > I reproduced the same problem in 2.3.1. I'm using two seed nodes with > hostnames vs. ip addresses. > Moving back to 2.3.0 resolved the issue. > > :) > > Brian - > > > On Friday, March 28, 2014 2:21:37 PM UTC-5, Patrik Nordwall wrote: > >> Hi Tommaso, >> Thanks for reporting. I will investigate on Monday. I'm not aware of any >> change that could cause this (famous last word). It would be useful if you >> can post logs at debug loglevel, including remote logging of remote send >> and receive. >> http://doc.akka.io/docs/akka/current/additional/faq.html# >> Which_options_shall_I_enable_when_debugging_remoting_issues_ >> >> /Patrik >> >> On Mar 28, 2014, at 17:46, Tommaso Paba <[email protected]> wrote: >> >> Hi, >> since we upgraded to Akka 2.3.1 (from version 2.3.0) we are experiencing >> a strange problem with clustering. >> More precisely, we are in a very simple situation where we have two seed >> nodes: >> >> cluster { >> seed-nodes = [ >> "akka.tcp://[email protected]:2551", >> "akka.tcp://[email protected]:2552"] >> auto-down-unreachable-after = 10s >> roles = ["worker"] >> } >> >> With Akka 2.3.0, we could start the first seed node, then start the >> second node, which joined the cluster, and everything worked fine. >> With Akka 2.3.1, we are noticing that the second seed node never actually >> joins the cluster. >> >> When the first seed node is started, here is what it logs: >> >> [Remoting] Starting remoting >> [Remoting] Remoting started; listening on addresses :[akka.tcp:// >> [email protected]:2551] >> Cluster Node [akka.tcp://[email protected]:2551] - Starting >> up... >> Cluster Node [akka.tcp://[email protected]:2551] - >> Registered cluster JMX MBean [akka:type=Cluster] >> Cluster Node [akka.tcp://[email protected]:2551] - Started >> up successfully >> Cluster Node [akka.tcp://[email protected]:2551] - Metrics >> collection has started successfully >> Association with remote system [akka.tcp://MyClusterSystem@ >> 192.168.1.147:2552] has failed, address is now gated for [5000] ms. >> Reason is: [Association failed with [akka.tcp://MyClusterSystem@ >> 192.168.1.147:2552]]. >> Cluster Node [akka.tcp://[email protected]:2551] - Node >> [akka.tcp://[email protected]:2551] is JOINING, roles >> [worker] >> Cluster Node [akka.tcp://[email protected]:2551] - Leader is >> moving node [akka.tcp://[email protected]:2551] to [Up] >> >> and we correctly receive the MemberUp message in our code. >> But when we start the second seed node, here's what happens: >> >> [Remoting] Starting remoting >> [Remoting] Remoting started; listening on addresses :[akka.tcp:// >> [email protected]:2552] >> Cluster Node [akka.tcp://[email protected]:2552] - Starting >> up... >> Cluster Node [akka.tcp://[email protected]:2552] - Registered >> cluster JMX MBean [akka:type=Cluster] >> Cluster Node [akka.tcp://[email protected]:2552] - Started up >> successfully >> Cluster Node [akka.tcp://[email protected]:2552] - Metrics >> collection has started successfully >> >> >> and that's all. The new member is never set to Up. >> >> If we switch back to Akka 2.3.0, everything works as expected, i.e. when >> the second seed node is started, it is set to Up and we correctly receive >> the MemberUp message. >> >> So my question is: is this a bug in Akka 2.3.1? Or maybe something has >> been changed? >> Has anyone experienced the same issue? >> >> TIA, >> Tommaso. >> >> -- >> >>>>>>>>>> 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. >> >> -- > >>>>>>>>>> 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 JOIN US. REGISTER TODAY! <http://www.scaladays.org/> Scala <http://www.scaladays.org/> Days <http://www.scaladays.org/> June 16th-18th, <http://www.scaladays.org/> Berlin <http://www.scaladays.org/> -- >>>>>>>>>> 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.
