>From the archives: >https://groups.google.com/forum/#!searchin/elasticsearch/1.4$20data$20node/elasticsearch/8pUwFld88tI/sBH7bB7rYzsJ
Same subject as mine. Started on the 13th. Anyways, I’m having the exact same issue. I’ve got a cluster on 1.3.4 (well, now I’ve upgraded it to 1.3.5). When I provision a new node with 1.4 and the cloud-aws plugin with the proper version (2.4.0), the new node will not come up and join the cluster and so a rolling upgrade does not appear possible. 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/5CF8216AA982AF47A8E6DEACA629D22B4EBF0DA6%40s-us-ex-6.US.R5S.com. For more options, visit https://groups.google.com/d/optout.
