Newer elasticsearch instance cannot join the cluster


(Jae) #1

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.
To view this discussion on the web visit 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.


(Jae) #2

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.
To view this discussion on the web visit 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.


(Jason Wee) #3

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 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.
To view this discussion on the web visit
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.

--
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.
To view this discussion on the web visit 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.


(simonw-2) #4

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 <javascript:>>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 <javascript:>.
To view this discussion on the web visit
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.

--
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.
To view this discussion on the web visit 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.


(system) #5