org.elasticsearch.transport.TransportSerializationException: Failed to deserialize response解决方案

错误信息

org.elasticsearch.transport.RemoteTransportException: [Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.state.ClusterStateResponse]]
Caused by: org.elasticsearch.transport.TransportSerializationException: Failed to deserialize response of type [org.elasticsearch.action.admin.cluster.state.ClusterStateResponse]
    at org.elasticsearch.transport.netty.MessageChannelHandler.handleResponse(MessageChannelHandler.java:180)
    at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:138)
    at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
    at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
    at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
    at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
    at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
    at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
    at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
    at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
    at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IndexOutOfBoundsException: Readable byte limit exceeded: 6243
    at org.jboss.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
    at org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:132)
    at org.elasticsearch.common.io.stream.FilterStreamInput.readByte(FilterStreamInput.java:39)
    at org.elasticsearch.common.io.stream.StreamInput.readString(StreamInput.java:254)
    at org.elasticsearch.common.settings.Settings.readSettingsFromStream(Settings.java:699)
    at org.elasticsearch.cluster.metadata.MetaData.readFrom(MetaData.java:678)
    at org.elasticsearch.cluster.metadata.MetaData$Builder.readFrom(MetaData.java:1212)
    at org.elasticsearch.cluster.ClusterState.readFrom(ClusterState.java:697)
    at org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:677)
    at org.elasticsearch.action.admin.cluster.state.ClusterStateResponse.readFrom(ClusterStateResponse.java:58)
    at org.elasticsearch.transport.netty.MessageChannelHandler.handleResponse(MessageChannelHandler.java:178)
    ... 23 common frames omitted

错误背景

今天在用java client 连接ES本地ES集群时死活连不上，但是同样的代码连接公司的ES集群是没有任何问题的。我之前测试本地ES集群的项目是可以连接的，这就很奇怪，搜索了一下错误，有说是ES集群的java版本号不一样，于是我不用集群模式，只用一台还是报这错，无语了。遂去ES社区去搜索这个问题，看到有个答案，顿时明白了错误的原因，原来是客户端版本号和ES服务端的版本号不一致导致的。（PS:公司用的版本号是ES2.x,而我本地用的还是ES1.x,项目中用的jar包是2.x的）

错误原因

ES的客户端版本号和ES的服务端版本号不一样

解决办法

统一客户端和服务端的版本号

参考资料：
[https://discuss.elastic.co/t/can-connect-with-http-but-not-through-java-api/8754/4] (ES社区相关问题)