# 1.4.0 data node can't join existing 1.3.4 cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [November 13, 2014, 8:29am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719 "2014-11-13T08:29:42Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [November 13, 2014, 8:29am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/1 "2014-11-13T08:29:42Z")
(using elasticsearch-cloud-aws 2.4) This should work, right? Or do I need to upgrade the cluster to 1.3.5 first? The connection fails after a few errors like: 2014-11-13 07:18:22,498 [WARN] org.elasticsearch.discovery.zen.ping.unicast - [Porcupine] failed to send ping to [[#cloud-i-b743e456-0][530-1d][inet[/10.186.145.210:9300]]] org.elasticsearch.transport.RemoteTransportException: [Nomad][inet[/10.186.145.210:9300]][internal:discovery/zen/unicast] Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [internal:discovery/zen/unicast] at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) ~[org.elasticsearch.elasticsearch-1.4.0.jar:na] -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/efd3232c-b22f-4f2b-94c4-c942b75e81bf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/efd3232c-b22f-4f2b-94c4-c942b75e81bf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Todd\_Kamin](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@Todd\_Kamin](https://discuss.elastic.co/u/Todd_Kamin)\ **Post date:** [November 13, 2014, 4:16pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/2 "2014-11-13T16:16:08Z")
I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using the elasticsearch-cloud-aws plugin 2.4. [2014-11-13 16:02:26,055][WARN][discovery.zen.ping.unicast] [White Fang] failed to send ping to [[#cloud-i-03f79bcb-0][localhost][inet[/10.0.0.76:9300]]] org.elasticsearch.transport.RemoteTransportException: [Kraven the Hunter][inet[/10.0.0.76:9300]][internal:discovery/zen/unicast] Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [internal:discovery/zen/unicast] at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [November 13, 2014, 6:05pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/3 "2014-11-13T18:05:16Z")
Do not mix 1.3 with 1.4 nodes, it does not work. Jörg On Thu, Nov 13, 2014 at 5:16 PM, Todd Kamin [todd@crowdtangle.com](mailto:todd@crowdtangle.com) wrote: > I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using > the elasticsearch-cloud-aws plugin 2.4. > > [2014-11-13 16:02:26,055][WARN][discovery.zen.ping.unicast] [White Fang] > failed to send ping to > [[#cloud-i-03f79bcb-0][localhost][inet[/10.0.0.76:9300]]] > org.elasticsearch.transport.RemoteTransportException: [Kraven the > Hunter][inet[/10.0.0.76:9300]][internal:discovery/zen/unicast] > Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: > No handler for action [internal:discovery/zen/unicast] > at > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) > at > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 13, 2014, 9:17pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/4 "2014-11-13T21:17:19Z")
Rolling upgrades should be supported: > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. How else can you perform a rolling upgrade without having a mixed cluster? -- Ivan On Thu, Nov 13, 2014 at 1:05 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > Do not mix 1.3 with 1.4 nodes, it does not work. > > Jörg > > On Thu, Nov 13, 2014 at 5:16 PM, Todd Kamin [todd@crowdtangle.com](mailto:todd@crowdtangle.com) wrote: > > > I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using > > the elasticsearch-cloud-aws plugin 2.4. > > > > [2014-11-13 16:02:26,055][WARN][discovery.zen.ping.unicast] [White Fang] > > failed to send ping to > > [[#cloud-i-03f79bcb-0][localhost][inet[/10.0.0.76:9300]]] > > org.elasticsearch.transport.RemoteTransportException: [Kraven the > > Hunter][inet[/10.0.0.76:9300]][internal:discovery/zen/unicast] > > Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: > > No handler for action [internal:discovery/zen/unicast] > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp\_9qB9G6z%2BSXUR7fqtB52\_A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp_9qB9G6z%2BSXUR7fqtB52_A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [November 13, 2014, 9:27pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/5 "2014-11-13T21:27:31Z")
I discovered a peculiarity, well documented in the source > > > The change in #7558 adds a flag to PingResponse. However, when unicast discovery… is used, this extra flag can not be serialized by the very initial pings as they do not know yet what node version they ping (i.e., they have to default to 1.0.0, which excludes changing the serialization format). This commit bypasses this problem by adding a dedicated action which only exist on nodes of version 1.4 or up. Nodes first try to ping this endpoint using 1.4.0 as a serialization version. If that fails they fall back to the pre 1.4.0 action. This is optimal if all nodes are on 1.4.0 or higher, with a small down side if the cluster has mixed versions - but this is a temporary state. > > Further two bwc protections are added: > 1) Disable the preference to nodes who previously joined the cluster if some of the pings are on version \< 1.4.0 > 2) Disable the rejoin on master gone functionality if some nodes in the cluster or version \< 1.4.0 > > Closes #7694 ``` /** * when pinging the initial configured target hosts, we do not know ``` their version. We therefore use \* the lowest possible version (i.e., 1.0.0) for serializing information on the wire. As of 1.4, we needed to extend \* the information sent in a ping, to prefer nodes which have previously joined the cluster during master election. \* This information is only needed if all the cluster is on version 1.4 or up. To bypass this issue we introduce \* a second action name which is guaranteed to exist only on nodes from version 1.4.0 and up. Using this action, \* we can safely use 1.4.0 as a serialization format. If this fails with a {@link ActionNotFoundTransportException} \* we know we speak to a node with \<1.4 version, and fall back to use {@link #ACTION\_NAME}. \*/ public static final String ACTION\_NAME\_GTE\_1\_4 = "internal:discovery/zen/unicast\_gte\_1\_4"; Not sure if everything works well... Jörg On Thu, Nov 13, 2014 at 10:17 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Rolling upgrades should be supported: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades) > > How else can you perform a rolling upgrade without having a mixed cluster? > > -- > Ivan > > On Thu, Nov 13, 2014 at 1:05 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< > [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > > > Do not mix 1.3 with 1.4 nodes, it does not work. > > > > Jörg > > > > On Thu, Nov 13, 2014 at 5:16 PM, Todd Kamin [todd@crowdtangle.com](mailto:todd@crowdtangle.com) wrote: > > > > > I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using > > > the elasticsearch-cloud-aws plugin 2.4. > > > > > > [2014-11-13 16:02:26,055][WARN][discovery.zen.ping.unicast] [White > > > Fang] failed to send ping to > > > [[#cloud-i-03f79bcb-0][localhost][inet[/10.0.0.76:9300]]] > > > org.elasticsearch.transport.RemoteTransportException: [Kraven the > > > Hunter][inet[/10.0.0.76:9300]][internal:discovery/zen/unicast] > > > Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: > > > No handler for action [internal:discovery/zen/unicast] > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:210) > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:111) > > > > > > -- > > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/840f26f7-c401-4229-b94d-092ee2ef4974%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGOOeMcuZqw7xADCuTc-MTQkuqQ0QtnBR%2Bg9TWBS6DOng%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp\_9qB9G6z%2BSXUR7fqtB52\_A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp_9qB9G6z%2BSXUR7fqtB52_A%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp\_9qB9G6z%2BSXUR7fqtB52\_A%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDrfhTAc6FhPpU-ZcHtW4Qp_9qB9G6z%2BSXUR7fqtB52_A%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFN06R7-sYGcsaUtg\_VagcjSHikbmPw%3DUSz-H29nvrmWA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFN06R7-sYGcsaUtg_VagcjSHikbmPw%3DUSz-H29nvrmWA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [November 13, 2014, 11:58pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/6 "2014-11-13T23:58:04Z")
On Thu, Nov 13, 2014 at 10:05 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Do not mix 1.3 with 1.4 nodes, it does not work. If that is so, that seems like something the release notes should mention? -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C\_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [November 14, 2014, 10:33am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/7 "2014-11-14T10:33:34Z")
I think this is only related to unicast. But, nevertheless, it _should_ work... not sure if this is a bug or a feature.... Jörg On Fri, Nov 14, 2014 at 12:58 AM, Eric Jain [eric.jain@gmail.com](mailto:eric.jain@gmail.com) wrote: > On Thu, Nov 13, 2014 at 10:05 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) > [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > > > Do not mix 1.3 with 1.4 nodes, it does not work. > > If that is so, that seems like something the release notes should mention? > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C\_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE7GvQiiz2G-PjNWXNKg5NWHE%2BUfwE0bg\_mHekw6e5WZw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE7GvQiiz2G-PjNWXNKg5NWHE%2BUfwE0bg_mHekw6e5WZw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Mads\_Martin\_Jorgense](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@Mads\_Martin\_Jorgense](https://discuss.elastic.co/u/Mads_Martin_Jorgense)\ **Post date:** [November 14, 2014, 11:41am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/8 "2014-11-14T11:41:08Z")
I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster with cloud-aws plugin version 2.4.0. Is there a workaround to use during upgrade, since I assume it's not a problem when they're all upgraded to 1.4.0. On Friday, November 14, 2014 11:33:45 AM UTC+1, Jörg Prante wrote: > I think this is only related to unicast. But, nevertheless, it _should_ > work... not sure if this is a bug or a feature.... > > Jörg > > On Fri, Nov 14, 2014 at 12:58 AM, Eric Jain \<[eric...@gmail.com](mailto:eric...@gmail.com) > \\> wrote: > > > On Thu, Nov 13, 2014 at 10:05 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \ > > \<[joerg...@gmail.com](mailto:joerg...@gmail.com) \\> wrote: > > > > > Do not mix 1.3 with 1.4 nodes, it does not work. > > > > If that is so, that seems like something the release notes should mention? > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C\_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/23b1428c-1e55-498e-ac8f-499adc8528e0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/23b1428c-1e55-498e-ac8f-499adc8528e0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Mads\_Martin\_Jorgense](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@Mads\_Martin\_Jorgense](https://discuss.elastic.co/u/Mads_Martin_Jorgense)\ **Post date:** [November 14, 2014, 1:25pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/9 "2014-11-14T13:25:20Z")
1.4.0 trying to join a 1.3.5 cluster with cloud-aws also fails. On Friday, November 14, 2014 12:41:08 PM UTC+1, [madsm...@colourbox.com](mailto:madsm...@colourbox.com) wrote: > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 > cluster with cloud-aws plugin version 2.4.0. Is there a workaround to use > during upgrade, since I assume it's not a problem when they're all upgraded > to 1.4.0. > > On Friday, November 14, 2014 11:33:45 AM UTC+1, Jörg Prante wrote: > > > I think this is only related to unicast. But, nevertheless, it _should_ > > work... not sure if this is a bug or a feature.... > > > > Jörg > > > > On Fri, Nov 14, 2014 at 12:58 AM, Eric Jain [eric...@gmail.com](mailto:eric...@gmail.com) wrote: > > > > > On Thu, Nov 13, 2014 at 10:05 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) > > > [joerg...@gmail.com](mailto:joerg...@gmail.com) wrote: > > > > > > > Do not mix 1.3 with 1.4 nodes, it does not work. > > > > > > If that is so, that seems like something the release notes should > > > mention? > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C\_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BKyW3nZ82uf1w1C_i3O9oW%3D%3DhG7f3WUC2-g40%3DwUn5Fgw%40mail.gmail.com) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/967ce7d9-3f53-4478-868b-85443a904620%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/967ce7d9-3f53-4478-868b-85443a904620%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Eric\_Jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eric_jain/32/834_2.png) [@Eric\_Jain](https://discuss.elastic.co/u/Eric_Jain)\ **Post date:** [November 14, 2014, 6:04pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/10 "2014-11-14T18:04:54Z")
On Fri, Nov 14, 2014 at 3:41 AM, [madsmartin@colourbox.com](mailto:madsmartin@colourbox.com) wrote: > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster > with cloud-aws plugin version 2.4.0. Is there a workaround to use during > upgrade, since I assume it's not a problem when they're all upgraded to > 1.4.0. I ended up starting a new cluster (ignoring all the warnings logged on startup), and restoring from a snapshot. Once all the 1.3.4 nodes were gone, no issues. -- Eric Jain Got data? Get answers at [zenobase.com](http://zenobase.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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BJ%2BfnBnus%3DOX6itdwcaB9%2Bh\_KDMwDYRBWU-4fWL0CohJA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BJ%2BfnBnus%3DOX6itdwcaB9%2Bh_KDMwDYRBWU-4fWL0CohJA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ElmerBeser](https://avatars.discourse-cdn.com/v4/letter/e/3d9bf3/32.png) [@ElmerBeser](https://discuss.elastic.co/u/ElmerBeser)\ **Post date:** [November 15, 2014, 8:50am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/11 "2014-11-15T08:50:02Z")
As soon as we surf the internet and looking for the jammer products we can see that there are various types of signal jammers that are for sale in the market now such as the mobile phone jammers, GPS jammers, wifi jammers, UHF jammers, **[video camera jamming device](http://www.jammerinthebox.com/categories/Wireless_Video%7B47%7DAudio_Signal_Jammer/)**, the multi-functional signal jammers and so many others kinds of signal jammers for sale as well. And what people now need to do is just select the best one according to their needs. ---
**Author:** ![Matthew\_Barrington](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matthew_barrington/32/1102_2.png) [@Matthew\_Barrington](https://discuss.elastic.co/u/Matthew_Barrington)\ **Post date:** [November 17, 2014, 11:13am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/12 "2014-11-17T11:13:22Z")
We are running a 1.3.4 cluster using the AWS plugin and I noticed the same error when I tried to upgrade a single node. Since I was trying this on my test cluster first I decided to see what would happen if I upgraded a 2nd node. Would it split into 2 clusters, have the same issue, etc. What I discovered was that when 2 nodes were upgraded to 1.4 they joined the cluster correctly and everything looks to be working. SO the problem seems to be for the initial node to join, but when you try with two everything works out. On Friday, 14 November 2014 18:05:01 UTC, Eric Jain wrote: > On Fri, Nov 14, 2014 at 3:41 AM, \<[madsm...@colourbox.com](mailto:madsm...@colourbox.com) \\> > wrote: > > > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 > > cluster > > with cloud-aws plugin version 2.4.0. Is there a workaround to use during > > upgrade, since I assume it's not a problem when they're all upgraded to > > 1.4.0. > > I ended up starting a new cluster (ignoring all the warnings logged on > startup), and restoring from a snapshot. Once all the 1.3.4 nodes were > gone, no issues. > > -- > Eric Jain > Got data? Get answers at [zenobase.com](http://zenobase.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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f618a79d-0a4f-4f97-8b89-ab6ccb9d1cbe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f618a79d-0a4f-4f97-8b89-ab6ccb9d1cbe%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Matthew\_Barrington](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matthew_barrington/32/1102_2.png) [@Matthew\_Barrington](https://discuss.elastic.co/u/Matthew_Barrington)\ **Post date:** [November 17, 2014, 11:35am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/13 "2014-11-17T11:35:03Z")
I stand corrected, this did not work on our main cluster. On Monday, 17 November 2014 11:13:22 UTC, Matthew Barrington wrote: > We are running a 1.3.4 cluster using the AWS plugin and I noticed the same > error when I tried to upgrade a single node. > > Since I was trying this on my test cluster first I decided to see what > would happen if I upgraded a 2nd node. Would it split into 2 clusters, have > the same issue, etc. > > What I discovered was that when 2 nodes were upgraded to 1.4 they joined > the cluster correctly and everything looks to be working. > > SO the problem seems to be for the initial node to join, but when you try > with two everything works out. > > On Friday, 14 November 2014 18:05:01 UTC, Eric Jain wrote: > > > On Fri, Nov 14, 2014 at 3:41 AM, [madsm...@colourbox.com](mailto:madsm...@colourbox.com) wrote: > > > > > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 > > > cluster > > > with cloud-aws plugin version 2.4.0. Is there a workaround to use > > > during > > > upgrade, since I assume it's not a problem when they're all upgraded to > > > 1.4.0. > > > > I ended up starting a new cluster (ignoring all the warnings logged on > > startup), and restoring from a snapshot. Once all the 1.3.4 nodes were > > gone, no issues. > > > > -- > > Eric Jain > > Got data? Get answers at [zenobase.com](http://zenobase.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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fc79c5e7-ddd6-4f52-9641-1bd01df3b866%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fc79c5e7-ddd6-4f52-9641-1bd01df3b866%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Christian\_Hedegaard](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@Christian\_Hedegaard](https://discuss.elastic.co/u/Christian_Hedegaard)\ **Post date:** [November 19, 2014, 1:39am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/14 "2014-11-19T01:39:49Z")
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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5CF8216AA982AF47A8E6DEACA629D22B4EBEEF75%40s-us-ex-6.US.R5S.com](https://groups.google.com/d/msgid/elasticsearch/5CF8216AA982AF47A8E6DEACA629D22B4EBEEF75%40s-us-ex-6.US.R5S.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [November 19, 2014, 10:27pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/15 "2014-11-19T22:27:15Z")
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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/16f33a69-fb07-4db1-9c05-b9031c867a63%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/16f33a69-fb07-4db1-9c05-b9031c867a63%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Christian\_Hedegaard](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@Christian\_Hedegaard](https://discuss.elastic.co/u/Christian_Hedegaard)\ **Post date:** [November 19, 2014, 10:43pm UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/16 "2014-11-19T22:43:38Z")
From the archives: [https://groups.google.com/forum/#!searchin/elasticsearch/1.4$20data$20node/elasticsearch/8pUwFld88tI/sBH7bB7rYzsJ](https://groups.google.com/forum/#!searchin/elasticsearch/1.4%2420data%2420node/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.leskes@gmail.com](mailto:b.leskes@gmail.com)] Sent: Wednesday, November 19, 2014 2:27 PM To: [elasticsearch@googlegroups.com](mailto: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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@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](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](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_Schonfeld](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@Daniel\_Schonfeld](https://discuss.elastic.co/u/Daniel_Schonfeld)\ **Post date:** [November 20, 2014, 4:50am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/17 "2014-11-20T04:50:27Z")
We use GCE and the GCE plugin, on initial load it seemed like what you are describing. Only when I examined the logs carefully i noticed that its more strict in reading the yaml and in our case the zone used to be cloud: gce: zone: ["us-central1-a","us-central1-f"] And with 1.4 it should now be: cloud: gce: zone: us-central1-a,us-central1-f I haven't looked into the AWS plugin, but perhaps it the same kind of strict yaml configuration read. Good luck! On Wednesday, November 19, 2014 5:43:49 PM UTC-5, Christian Hedegaard wrote: > From the archives: > [Redirecting to Google Groups](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.le...@gmail.com](mailto:b.le...@gmail.com) \] > _Sent:_ Wednesday, November 19, 2014 2:27 PM > _To:_ [elasti...@googlegroups.com](mailto:elasti...@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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/294e7c85-10a0-4975-a3ef-12fd106cd69c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/294e7c85-10a0-4975-a3ef-12fd106cd69c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Christian\_Hedegaard](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@Christian\_Hedegaard](https://discuss.elastic.co/u/Christian_Hedegaard)\ **Post date:** [November 21, 2014, 12:56am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/18 "2014-11-21T00:56:59Z")
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.leskes@gmail.com](mailto:b.leskes@gmail.com)] Sent: Wednesday, November 19, 2014 2:27 PM To: [elasticsearch@googlegroups.com](mailto: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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@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](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](https://groups.google.com/d/optout). ---
**Author:** ![Mads\_Martin\_Jorgense](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@Mads\_Martin\_Jorgense](https://discuss.elastic.co/u/Mads_Martin_Jorgense)\ **Post date:** [November 21, 2014, 9:02am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/19 "2014-11-21T09:02:31Z")
Is there any of the elasticsearch team members that can hint to whether or not this is something that will be fixed in 1.4.1? Then we'll simply wait for it instead of doing different hacks to upgrade. On Monday, November 17, 2014 12:35:03 PM UTC+1, Matthew Barrington wrote: > I stand corrected, this did not work on our main cluster. > > On Monday, 17 November 2014 11:13:22 UTC, Matthew Barrington wrote: > > > We are running a 1.3.4 cluster using the AWS plugin and I noticed the > > same error when I tried to upgrade a single node. > > > > Since I was trying this on my test cluster first I decided to see what > > would happen if I upgraded a 2nd node. Would it split into 2 clusters, have > > the same issue, etc. > > > > What I discovered was that when 2 nodes were upgraded to 1.4 they joined > > the cluster correctly and everything looks to be working. > > > > SO the problem seems to be for the initial node to join, but when you try > > with two everything works out. > > > > On Friday, 14 November 2014 18:05:01 UTC, Eric Jain wrote: > > > > > On Fri, Nov 14, 2014 at 3:41 AM, [madsm...@colourbox.com](mailto:madsm...@colourbox.com) wrote: > > > > > > > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 > > > > cluster > > > > with cloud-aws plugin version 2.4.0. Is there a workaround to use > > > > during > > > > upgrade, since I assume it's not a problem when they're all upgraded > > > > to > > > > 1.4.0. > > > > > > I ended up starting a new cluster (ignoring all the warnings logged on > > > startup), and restoring from a snapshot. Once all the 1.3.4 nodes were > > > gone, no issues. > > > > > > -- > > > Eric Jain > > > Got data? Get answers at [zenobase.com](http://zenobase.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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 21, 2014, 9:06am UTC](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719/20 "2014-11-21T09:06:32Z")
It's being looked at, but I don't know much beyond that at the moment sorry. On 21 November 2014 20:02, [madsmartin@colourbox.com](mailto:madsmartin@colourbox.com) wrote: > Is there any of the elasticsearch team members that can hint to whether or > not this is something that will be fixed in 1.4.1? Then we'll simply wait > for it instead of doing different hacks to upgrade. > > On Monday, November 17, 2014 12:35:03 PM UTC+1, Matthew Barrington wrote: > > > I stand corrected, this did not work on our main cluster. > > > > On Monday, 17 November 2014 11:13:22 UTC, Matthew Barrington wrote: > > > > > We are running a 1.3.4 cluster using the AWS plugin and I noticed the > > > same error when I tried to upgrade a single node. > > > > > > Since I was trying this on my test cluster first I decided to see what > > > would happen if I upgraded a 2nd node. Would it split into 2 clusters, have > > > the same issue, etc. > > > > > > What I discovered was that when 2 nodes were upgraded to 1.4 they joined > > > the cluster correctly and everything looks to be working. > > > > > > SO the problem seems to be for the initial node to join, but when you > > > try with two everything works out. > > > > > > On Friday, 14 November 2014 18:05:01 UTC, Eric Jain wrote: > > > > > > > On Fri, Nov 14, 2014 at 3:41 AM, [madsm...@colourbox.com](mailto:madsm...@colourbox.com) wrote: > > > > > > > > > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 > > > > > cluster > > > > > with cloud-aws plugin version 2.4.0. Is there a workaround to use > > > > > during > > > > > upgrade, since I assume it's not a problem when they're all upgraded > > > > > to > > > > > 1.4.0. > > > > > > > > I ended up starting a new cluster (ignoring all the warnings logged on > > > > startup), and restoring from a snapshot. Once all the 1.3.4 nodes were > > > > gone, no issues. > > > > > > > > -- > > > > Eric Jain > > > > Got data? Get answers at [zenobase.com](http://zenobase.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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/312dcdc1-d826-4cb9-b480-620232634ea7%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZn-ryDDoQps-smzUPkJd5ru9EHfKuAGRReU2-J-C35kvA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZn-ryDDoQps-smzUPkJd5ru9EHfKuAGRReU2-J-C35kvA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). [Next page](https://discuss.elastic.co/t/1-4-0-data-node-cant-join-existing-1-3-4-cluster/20719.md?page=2)