Are you using a TransportClient or NodeClient?
If NodeClient, could you try with the TransportClient?
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 11 juillet 2014 à 11:14:59, xzer LR (xiao...@gmail.com) a écrit:
As a test result, I got exceptions when I tried to use the newest 1.2.2 java
client to connect to a 1.0.3 cluster:
18:05:41.020 [elasticsearch[Slipstream][transport_client_worker][T#1]{New I/O
worker #1}] [INFO ] [] org.elasticsearch.client.transport[105] - [Slipstream]
failed to get local cluster state for
[#transport#-1][e-note][inet[/192.168.200.81:9300]], disconnecting...
org.elasticsearch.transport.RemoteTransportException:
[server-cat][inet[/192.168.21.81:9300]][cluster/state]
java.lang.IndexOutOfBoundsException: Readable byte limit exceeded: 48
at
org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:132)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:141)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.common.io.stream.StreamInput.readString(StreamInput.java:272)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readString(HandlesStreamInput.java:61)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.common.io.stream.StreamInput.readStringArray(StreamInput.java:362)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.action.admin.cluster.state.ClusterStateRequest.readFrom(ClusterStateRequest.java:132)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:209)
~[elasticsearch-1.2.2.jar:na]
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:109)
~[elasticsearch-1.2.2.jar:na]
I didn't find any metioned break change about this exceptioin.
在 2014年7月4日星期五UTC+9下午3时31分07秒，David Pilato写道：
Well. It depends.
1.0 is incompatible with 0.90
1.2 should work with 1.x IIRC.
>From 1.0, we try to keep this compatible. If not, release notes will tell you.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 4 juil. 2014 à 07:09, xzer LR <xia...@gmail.com> a écrit :
For some reasons, we have several separated elasticsearch clusters for our
front applicaitons. We want to upgrade our clusters' version to the newest
version but apparently it is impossible to upgrade all the clusters at the same
time, which means our single application have to connect to multiple clusters
with different versions.
My question is whether the elasticsearch java client has the ability to work
correctly with an old version server?
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/baa98ec5-ffcf-46f9-bfdd-7afbd213b19d%40googlegroups.com.
For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/77e32825-812a-46c8-82b4-93a5e4b12788%40googlegroups.com.
For more options, visit 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/etPan.53bfb38f.1190cde7.70e%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
