FYI, I have found a solution that works (at least for me). I’ve got a small cluster for testing, only 4 v1.3.5 nodes. What I’ve done is bring up 4X new v1.4.0 nodes as data-only machines. In the yaml I added a line to point the nodes via unicast explicitly to the current master: discovery.zen.ping.unicast.hosts: ["10.210.9.224:9300"]
When I restarted elasticsearch with that setting, with cloud-aws installed and configured on version 2.4.0, the new nodes found the cluster and properly joined it. I will now start nuking the old v1.3.5 nodes to migrate the data off of them. Before the final 1.3.5 node is nuked, I will change the config on one of the v1.4.0 nodes to allow it as master and restart it. I’m not sure if the master stuff is needed or not, but I was very afraid of a split-brain problem. I have another 4-node testing cluster that I will be able to try this upgrade again with in a more controlled manner. I’m NOT looking forward to upgrading our current production cluster this way (15 data-only nodes, 3 master-only nodes). So it would appear that the problem is somewhere in the unicast discovery code. The question is who’s to blame? Elasticsearch or the cloud-aws plugin? From: Boaz Leskes [mailto:b.les...@gmail.com] Sent: Wednesday, November 19, 2014 2:27 PM To: elasticsearch@googlegroups.com Cc: Christian Hedegaard Subject: Re: 1.4.0 data node can't join existing 1.3.4 cluster Hi Christian, I'm not sure what thread you refer to exactly, but this shouldn't happen. Can you describe the problem you have some more? Anything in the nodes? (both the 1.4 node and the master) Cheers, Boaz On Wednesday, November 19, 2014 2:39:57 AM UTC+1, Christian Hedegaard wrote: I found this thread while trying to research the same issue and it looks like there is currently no resolution. We like to keep up on our elasticsearch upgrades as often as possible and do rolling upgrades to keep our clusters up. When testing I’m having the same issue, I cannot add a 1.4.0 box to the existing 1.3.4 cluster. Is there a fix for this anticipated? -- 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/5CF8216AA982AF47A8E6DEACA629D22B4EBF409B%40s-us-ex-6.US.R5S.com. For more options, visit https://groups.google.com/d/optout.
