# Updated to 2.2.0 and now seeing "Message not fully read (request)" **URL:** \ **Category:** Elasticsearch\ **Created:** [February 5, 2016, 11:55pm UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105 "2016-02-05T23:55:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![polloelastico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polloelastico/32/7631_2.png) [@polloelastico](https://discuss.elastic.co/u/polloelastico)\ **Post date:** [February 5, 2016, 11:55pm UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/1 "2016-02-05T23:55:13Z")
I have 5 nodes in a cluster on AWS and am using the cloud-aws plugin, there are 3 data nodes and 2 non-data nodes. The logs in the non-data nodes are filling up with the following: [2016-02-05 23:51:18,055][WARN][transport.netty] [elasticsearch-balancer1.localdomain] exception caught on transport layer [[id: 0x60afa850, /172.31.26.143:28587 =\> /172.31.34.64:9300]], closing connection java.lang.IllegalStateException: Message not fully read (request) for requestId [1699053], action [cluster/nodes/info], readerIndex [39] vs expected [57]; resetting at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:120) 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$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:75) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ^C The 3 data nodes do not have this error. I am at a loss for what this could mean. Anyone have any ideas? Thanks, ---
**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:** [February 6, 2016, 1:25am UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/2 "2016-02-06T01:25:36Z")
At an educated guess it looks like you may have clients connecting that aren't the same version? ---
**Author:** ![polloelastico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polloelastico/32/7631_2.png) [@polloelastico](https://discuss.elastic.co/u/polloelastico)\ **Post date:** [February 6, 2016, 2:10am UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/3 "2016-02-06T02:10:52Z")
Ah, could be! I just updated the ES cluster and didn't get around to the clients yet; the clients hit the non-data nodes of course. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 6, 2016, 5:24am UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/4 "2016-02-06T05:24:04Z")
I'm curious about the version you were using in clients? ---
**Author:** ![polloelastico](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polloelastico/32/7631_2.png) [@polloelastico](https://discuss.elastic.co/u/polloelastico)\ **Post date:** [February 6, 2016, 5:40am UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/5 "2016-02-06T05:40:31Z")
Clients were on 1.7.3 while the cluster was running 2.2.0. Once all the clients were updated, the error was resolved. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 6, 2016, 8:10am UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/6 "2016-02-06T08:10:38Z")
Ah! Great to know. Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:18pm UTC](https://discuss.elastic.co/t/updated-to-2-2-0-and-now-seeing-message-not-fully-read-request/41105/7 "2017-07-05T23:18:27Z")