Hi, when discovering seed nodes dynamically, why is it important for every node (except for one) to not include itself in the seed node list? How could split brain happen if all nodes have the same list order of all seed nodes?
>From what I understand, split-brain can only happen if multiple nodes put themselves first in the seed node list, is that correct? I ask because when doing static configuration, it's common for all nodes to have the same seed node list, which means all seed nodes would have themselves in the list. And that seems to be common, recommended practice. If doing dynamic discovery of seed nodes, is it okay for all nodes to have the same list of seed nodes, if we can guarantee they are all in the same order? From reading the docs, I gather that after sending a message to all seed nodes, if none respond, then it will try to join the first node in the list, which wouldn't work if the first node in the list isn't itself. We are considering using the AWS SDK by not querying the ASG for its instance list until the cloudformation stack says it is complete, which should guarantee that all nodes trying to join the cluster will get the same list of instances in the ASG. Then we can guarantee that all nodes would order the nodes the same - any reason this wouldn't work? Thanks, Curt -- >>>>>>>>>> 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.
