Hi Konrad, thanks for your answer. Upgrading akka was my first intention. Unfortunately, due "bureaucratic" stuff I'm not allowed to do it. Regarding actors, they are not doing anything. There is one actor per node and they are not sending any message whatsoever. I just connect the nodes and wait for sometime, and suddenly one of them start failling with this AssociationError. The curious thing is, this is only happening when I use VM's to startup nodes. If I start up nodes on a single computer, it works like a charm, but going to the server and deploy each node on a separate VM, causes this.
Do you know if using VM need some sort of special network configuration and/or is known to give problems? Thanks a lot El miércoles, 30 de agosto de 2017, 7:32:49 (UTC-3), Konrad Malawski escribió: > > What are your actors doing? Are you blocking somewhere? > > It should “just work”. > > Please upgrade to an actually maintained version too please - 2.3 is very > ancient, > please use the current release timeline 2.5 – there should be almost no > code changes you need to do btw, it’s compatible. > > — > Konrad `kto.so` Malawski > Akka <http://akka.io> @ Lightbend <http://lightbend.com> > > On 30 August 2017 at 18:47:40, Rodrigo Silva (rodrig...@wazoo.com.ar > <javascript:>) wrote: > > > I'm using akka 2.3.14 and I set up to use Remote and Cluster features with > this basic set up: > > akka { > actor { > provider = "akka.cluster.ClusterActorRefProvider" > } > remote { > netty.tcp { > hostname = someIP > port = SOMEPORT > } > } > > cluster { > seed-nodes = [ > "akka.tcp://ClusterSystem@SOMEFIXEDIP:9191"] > > auto-down-unreachable-after = 120s > } > } > > > > I been able to start up to 40 nodes on the same machine (for testing > purposes). Same thing with 2 machines, and even with one or two virtual > machines. > > The problem arises when I set up 8 virtual machines on a server, each > running one single node. There is no custom code being executed, I just > manage to start up an actor system and I see them getting connected each > other. After a while being idle, I start seeing things like this on a node: > > [WARN] [08/24/2017 12:32:53.125] [ClusterSystem-akka.remote.default-remote > -dispatcher-6] > [akka.tcp://ClusterSystem@vm-euler-04:7887/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40euler%3A9191-0] > > Association with remote system [akka.tcp://ClusterSystem@euler:9191] has > failed, address is now gated for [5000] ms. Reason: [Disassociated] > [WARN] [08/24/2017 12:32:53.141] [ClusterSystem-akka.remote.default-remote > -dispatcher-5] > [akka.tcp://ClusterSystem@vm-euler-04:7887/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40vm-euler-02%3A7887-2] > > Association with remote system [akka.tcp://ClusterSystem@vm-euler-02:7887] > has failed, address is now gated for [5000] ms. Reason: [Disassociated] > [WARN] [08/24/2017 12:32:53.531] [ClusterSystem-akka.remote.default-remote > -dispatcher-5] > [akka.tcp://ClusterSystem@vm-euler-04:7887/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40vm-euler-01%3A7887-3] > > Association with remote system [akka.tcp://ClusterSystem@vm-euler-01:7887] > has failed, address is now gated for [5000] ms. Reason: [Disassociated] > ... > [ERROR] [08/24/2017 12:33:00.078] [ClusterSystem-akka.remote.default- > remote-dispatcher-25] > [akka.tcp://ClusterSystem@vm-euler-04:7887/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40vm-euler-03%3A7887-1/endpointWriter] > > AssociationError [akka.tcp://ClusterSystem@vm-euler-04:7887] -> > [akka.tcp://ClusterSystem@vm-euler-03:7887]: Error [Invalid address: > akka.tcp://ClusterSystem@vm-euler-03:7887] [ > akka.remote.InvalidAssociation: Invalid address: akka.tcp: > //ClusterSystem@vm-euler-03:7887 > Caused by: akka.remote.transport.Transport$InvalidAssociationException: > The remote system has quarantined this system. No further associations to > the remote system are possible until this system is restarted. > ] > > > > What puzzles me is, first, nodes gets connected at the very begging and > second, it start failing when 8 or more VM are created and launched. And > second, log information doesn't say much. > > Is there any way to get more information about what is going on > here?(log level, trace, dump...) > Do I need special set up when it comes to use virtual machines? I > mean, starting up 40 nodes on the same cpu didn't got disconnected. > > -- > >>>>>>>>>> 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 akka-user+...@googlegroups.com <javascript:>. > To post to this group, send email to akka...@googlegroups.com > <javascript:>. > Visit this group at https://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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
