# Newer elasticsearch instance cannot join the cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [January 11, 2014, 9:22am UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206 "2014-01-11T09:22:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\ **Post date:** [January 11, 2014, 9:22am UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206/1 "2014-01-11T09:22:22Z")
Hello, I am running 0.90.2 cluster and I want to upgrade it to 0.90.10. I created a new instance with 0.90.10 and I expected it would join to the legacy cluster but with the following error, it couldn't join. The new instance doesn't have any data and I was expecting newly joined instance would copy the replica from the old one. 2014-01-11 08:42:26,070 INFO org.elasticsearch.common.logging.log4j.Log4jESLogger:114 [elasticsearch[...][generic][T#1]] [internalInfo] [i-6d71a643] failed to send join request to master [...][\_dmbrG14Tcy2nkySP-xcoA][inet[/...:7102]]{rack\_id=us-east-1e}], reason [org.elasticsearch.transport.RemoteTransportException: [i-5b6a683c][inet[/...:7102]][discovery/zen/join]; org.elasticsearch.transport.RemoteTransportException: [i-6d71a643][inet[/...:7102]][discovery/zen/join/validate]; java.io.IOException: Expected handle header, got [17]] I guess 'Expected handle header' error usually occurs when mixed versions of ES are used but is this normal procedure of rolling upgrade of elasticsearch? Thank you Best, Jae -- 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/623089b1-8f6b-4151-b16a-8bfc494b5696%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/623089b1-8f6b-4151-b16a-8bfc494b5696%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\ **Post date:** [January 12, 2014, 4:25am UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206/2 "2014-01-12T04:25:25Z")
Upgrading 0.90.2 -\> 0.90.3 -\> 0.90.10 is possible but direct upgrade from 0.90.2 to 0.90.10 isn't possible due to version mismatch. On Saturday, January 11, 2014 1:22:22 AM UTC-8, Jae wrote: > Hello, I am running 0.90.2 cluster and I want to upgrade it to 0.90.10. > > I created a new instance with 0.90.10 and I expected it would join to the > legacy cluster but with the following error, it couldn't join. The new > instance doesn't have any data and I was expecting newly joined instance > would copy the replica from the old one. > > 2014-01-11 08:42:26,070 INFO > org.elasticsearch.common.logging.log4j.Log4jESLogger:114 > [elasticsearch[...][generic][T#1]] [internalInfo] [i-6d71a643] failed to > send join request to master > [...][\_dmbrG14Tcy2nkySP-xcoA][inet[/...:7102]]{rack\_id=us-east-1e}], reason > [org.elasticsearch.transport.RemoteTransportException: > [i-5b6a683c][inet[/...:7102]][discovery/zen/join]; > org.elasticsearch.transport.RemoteTransportException: > [i-6d71a643][inet[/...:7102]][discovery/zen/join/validate]; > java.io.IOException: Expected handle header, got [17]] > > I guess 'Expected handle header' error usually occurs when mixed versions > of ES are used but is this normal procedure of rolling upgrade of > elasticsearch? > > Thank you > Best, Jae -- 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/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\ **Post date:** [January 13, 2014, 12:40am UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206/3 "2014-01-13T00:40:47Z")
Hi, for es version 0.90.2 using lucene 4.3.1 and for es version 0.90.7 using lucene version 4.5.1 and es version 0.90.8 using lucene 4.6.0. Are you sure you upgraded successfully with the index/query still functional work? /Jason On Sun, Jan 12, 2014 at 12:25 PM, Jae [metacret@gmail.com](mailto:metacret@gmail.com) wrote: > Upgrading 0.90.2 -\> 0.90.3 -\> 0.90.10 is possible but direct upgrade from > 0.90.2 to 0.90.10 isn't possible due to version mismatch. > > On Saturday, January 11, 2014 1:22:22 AM UTC-8, Jae wrote: > > > Hello, I am running 0.90.2 cluster and I want to upgrade it to 0.90.10. > > > > I created a new instance with 0.90.10 and I expected it would join to the > > legacy cluster but with the following error, it couldn't join. The new > > instance doesn't have any data and I was expecting newly joined instance > > would copy the replica from the old one. > > > > 2014-01-11 08:42:26,070 INFO org.elasticsearch.common. > > logging.log4j.Log4jESLogger:114 [elasticsearch[...][generic][T#1]] > > [internalInfo] [i-6d71a643] failed to send join request to master > > [...][\_dmbrG14Tcy2nkySP-xcoA][inet[/...:7102]]{rack\_id=us-east-1e}], > > reason [org.elasticsearch.transport.RemoteTransportException: > > [i-5b6a683c][inet[/...:7102]][discovery/zen/join]; > > org.elasticsearch.transport.RemoteTransportException: > > [i-6d71a643][inet[/...:7102]][discovery/zen/join/validate]; > > java.io.IOException: Expected handle header, got [17]] > > > > I guess 'Expected handle header' error usually occurs when mixed versions > > of ES are used but is this normal procedure of rolling upgrade of > > elasticsearch? > > > > Thank you > > Best, Jae > > -- > 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/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAHO4ityGpq\_YCzkYEmzKSWJAi1E5xvukT1z%2BP%3DFOFat8cLmb\_A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4ityGpq_YCzkYEmzKSWJAi1E5xvukT1z%2BP%3DFOFat8cLmb_A%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [January 13, 2014, 11:23pm UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206/4 "2014-01-13T23:23:08Z")
All these version are backwards compatible. You can safely upgrade a lucene index from 4.3.1 to 4.5.1 or 4.6.0. You can't downgrade so they are not forward compatible though! simon On Monday, January 13, 2014 1:40:47 AM UTC+1, Jason Wee wrote: > Hi, for es version 0.90.2 using lucene 4.3.1 and for es version 0.90.7 > using lucene version 4.5.1 and es version 0.90.8 using lucene 4.6.0. Are > you sure you upgraded successfully with the index/query still functional > work? > > /Jason > > On Sun, Jan 12, 2014 at 12:25 PM, Jae \<[meta...@gmail.com](mailto:meta...@gmail.com) \\>wrote: > > > Upgrading 0.90.2 -\> 0.90.3 -\> 0.90.10 is possible but direct upgrade from > > 0.90.2 to 0.90.10 isn't possible due to version mismatch. > > > > On Saturday, January 11, 2014 1:22:22 AM UTC-8, Jae wrote: > > > > > Hello, I am running 0.90.2 cluster and I want to upgrade it to 0.90.10. > > > > > > I created a new instance with 0.90.10 and I expected it would join to > > > the legacy cluster but with the following error, it couldn't join. The new > > > instance doesn't have any data and I was expecting newly joined instance > > > would copy the replica from the old one. > > > > > > 2014-01-11 08:42:26,070 INFO org.elasticsearch.common. > > > logging.log4j.Log4jESLogger:114 [elasticsearch[...][generic][T#1]] > > > [internalInfo] [i-6d71a643] failed to send join request to master > > > [...][\_dmbrG14Tcy2nkySP-xcoA][inet[/...:7102]]{rack\_id=us-east-1e}], > > > reason [org.elasticsearch.transport.RemoteTransportException: > > > [i-5b6a683c][inet[/...:7102]][discovery/zen/join]; > > > org.elasticsearch.transport.RemoteTransportException: > > > [i-6d71a643][inet[/...:7102]][discovery/zen/join/validate]; > > > java.io.IOException: Expected handle header, got [17]] > > > > > > I guess 'Expected handle header' error usually occurs when mixed > > > versions of ES are used but is this normal procedure of rolling upgrade of > > > elasticsearch? > > > > > > Thank you > > > Best, Jae > > > > -- > > 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/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/57546a30-08e0-4f75-9beb-3ff3d1705b62%40googlegroups.com) > > . > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/66a6ec24-5580-4039-87ef-f45006792032%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/66a6ec24-5580-4039-87ef-f45006792032%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:57am UTC](https://discuss.elastic.co/t/newer-elasticsearch-instance-cannot-join-the-cluster/15206/5 "2017-07-06T01:57:04Z")