> yes of course in one work: unicast seems like an overhead ... , think > of a scenario that you need to add more nodes to the cluster (pretty > common one for us) you need to change the yml config on each node and > restart the cluster Node by Node making sure that all other nodes > "sees" the new node ....
I'm pretty sure this is incorrect actually. I suspect if you had added some existing nodes' IPs to the discovery list on the new node, all the nodes would have formed a cluster. Information about what nodes are in the cluster is stored canonically on the master and replicated around - once a node is known about, its existence should be communicated to the other nodes. Cheers, Dan -- Dan Fairs | dan.fa...@gmail.com | @danfairs | secondsync.com -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/E997488E-7B62-4966-9074-68F55A7345EA%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
