If you can set the IPs of your seed node(s) upfront and put them into configuration of every node all is fine and well. Unfortunately this is not what happens in a dynamic environment, hence the need to elect the seed node before Akka cluster boots up.
Cheers, Rafał W dniu środa, 28 grudnia 2016 11:56:56 UTC+1 użytkownik Evgeny Shepelyuk napisał: > > Hello > > Do you mean that in AKKA cluster there's only one seed node ? > I thought AKKA cluster may have several seed node, so new instances can > connect to any of them. > AKKA documentations show example with multiple seed nodes. > > середа, 28 грудня 2016 р. 12:48:33 UTC+2 користувач Rafał Krzewski написав: >> >> Evgeny, >> The role of etcd / consul / zookeeper in the booting up an Akka cluster >> is to provide a distributed lock rather than service discovery. When you >> boot up a number of uniform nodes they need to decide among themselves >> which one will act as a seed of Akka cluster. The other nodes then join the >> seed. An external service that provides consistency guarantees prevents the >> cluster from brain-splitting at the very outset. I'm not familiar with >> docker-swarm feature set, but unless it provides a strongly consistent KV >> store or other means of distributed coordination, this is not going to fly. >> >> Cheers, >> Rafał >> >> -- >>>>>>>>>> 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.
