I guess this could happen when node 1 starts up and later on node 2 starts
up and for some reason cannot connect to running node 1. The more nodes in
the cluster, when all of them are listed, the less likelihood of this
happening though one of the nodes coming up online later could have issues
I guess this could happen when node 1 starts up and later on node 2 starts
up and for some reason cannot connect to running node 1. The more nodes in
the cluster, when all of them are listed, the less likelihood of this
happening, but I see your point.
Thanks,
Andre
On Wednesday, January 6, 20
When starting a new cluster (no existing nodes) you would risk that each
node joins itself and thereby creating many separate clusters.
>From docs:
The seed nodes can be started in any order and it is not necessary to have
all seed nodes running, but the node configured as the first element in the
With akka-cluster 2.3.11 I seem to be able to have configuration below work
as well, contrary to the claim here (
https://groups.google.com/forum/#!searchin/akka-user/seed$20node/akka-user/Wehd8AcN1pw/Tc0PYBq2DQAJ)
that it doesn't work.
Node 1:
akka.remote.netty.tcp.hostname = 127.0.0.1
akka.re
I'm not sure I understand your problem. You should used something like this:
Node 1:
akka.remote.netty.tcp.hostname = 127.0.0.1
akka.remote.netty.tcp.port = 2551
akka.cluster.seed-nodes = ["akka.tcp://ClusterSystem@127.0.0.1:2551
", "akka.tcp://ClusterSystem@127.0.0.1:2552"]
Node 2:
akka.remote.n
Hi,
I am working with akka distributed worker template available on typesafe. I
am using it to write a backend job which takes data from siebel using soap
calls and inserts in mongo. This job is supposed to run once a week for few
hours.
Based on the cluster-usage and other documentation on AK
