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 connecting to all other seed nodes. I see your point. It is probably better to have such node uninitialized and hope that connectivity be restored later on than running it as its own cluster.
Thanks, Andre On Wednesday, January 6, 2016 at 11:54:12 AM UTC-8, Patrik Nordwall wrote: > > 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 > seed-nodes configuration list must be started when initially starting a > cluster, otherwise the other seed-nodes will not become initialized and no > other node can join the cluster. The reason for the special first seed node > is to avoid forming separated islands when starting from an empty cluster > -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
