# "Message not fully read (response)" after upgrading 0.90.0 to 0.90.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [July 19, 2013, 3:51pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860 "2013-07-19T15:51:23Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Dave\_Konopka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dave_konopka/32/2235_2.png) [@Dave\_Konopka](https://discuss.elastic.co/u/Dave_Konopka)\ **Post date:** [July 19, 2013, 3:51pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/1 "2013-07-19T15:51:23Z")
We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one of the nodes is intermittently showing messages like these in the logs: [transport.netty] Message not fully read (response) for [12652] handler org. elasticsearch.action.support.master. TransportMasterNodeOperationAction$4@53854b5f, error [true], resetting I saw an earlier thread that this could be an issue with 0.90.0 that was fixed in 0.90.1. Odd though that it seems to have started for us with 0.90.1 Anyone have any thoughts or suggestions? The nodes are all running java version "1.6.0\_27" openjdk. { "ok" : true, "status" : 200, "name" : "...", "version" : { "number" : "0.90.1", "snapshot\_build" : false, "lucene\_version" : "4.3" }, "tagline" : "You Know, for Search" } Cluster health: { "cluster\_name" : "staging\_cluster", "status" : "green", "timed\_out" : false, "number\_of\_nodes" : 3, "number\_of\_data\_nodes" : 3, "active\_primary\_shards" : 9, "active\_shards" : 19, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 0 } -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [July 19, 2013, 4:35pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/2 "2013-07-19T16:35:53Z")
Oracle (formerly Sun) Java is good. Java 6 works for me (political reasons keep me from going to Java 7 at the moment), though java 7 is recommended. OpenJDK is not good. It's "exactly the same as Oracle Java, except that it's different". And it's those little differences that will cripple your application with strange and unpredictable failures. On Friday, July 19, 2013 11:51:23 AM UTC-4, Dave Konopka wrote: > We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one of > the nodes is intermittently showing messages like these in the logs: > > [transport.netty] Message not fully read (response) for [12652] handler > org.elasticsearch.action.support.master. > TransportMasterNodeOperationAction$4@53854b5f, error [true], resetting > > I saw an earlier thread that this could be an issue with 0.90.0 that was > fixed in 0.90.1. Odd though that it seems to have started for us with 0.90.1 > > Anyone have any thoughts or suggestions? > > The nodes are all running java version "1.6.0\_27" openjdk. > > { > "ok" : true, > "status" : 200, > "name" : "...", > "version" : { > "number" : "0.90.1", > "snapshot\_build" : false, > "lucene\_version" : "4.3" > }, > "tagline" : "You Know, for Search" > } > > Cluster health: > { > "cluster\_name" : "staging\_cluster", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 3, > "number\_of\_data\_nodes" : 3, > "active\_primary\_shards" : 9, > "active\_shards" : 19, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 0 > } -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Dave\_Konopka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dave_konopka/32/2235_2.png) [@Dave\_Konopka](https://discuss.elastic.co/u/Dave_Konopka)\ **Post date:** [July 19, 2013, 7:45pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/3 "2013-07-19T19:45:27Z")
We've been running OpenJDK for a while without issues. This only started happening after the upgrade to 0.90.1. Is Oracle Java recommended officially over OpenJDK? On Fri, Jul 19, 2013 at 12:35 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote: > Oracle (formerly Sun) Java is good. Java 6 works for me (political reasons > keep me from going to Java 7 at the moment), though java 7 is recommended. > > OpenJDK is not good. It's "exactly the same as Oracle Java, except that > it's different". And it's those little differences that will cripple your > application with strange and unpredictable failures. > > On Friday, July 19, 2013 11:51:23 AM UTC-4, Dave Konopka wrote: > > > We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one > > of the nodes is intermittently showing messages like these in the logs: > > > > [transport.netty] Message not fully read (response) for [12652] handler > > org.elasticsearch.action.suppo **rt.master.TransportMasterNodeO** > > perationAction$4@53854b5f, error [true], resetting > > > > I saw an earlier thread that this could be an issue with 0.90.0 that was > > fixed in 0.90.1. Odd though that it seems to have started for us with 0.90.1 > > > > Anyone have any thoughts or suggestions? > > > > The nodes are all running java version "1.6.0\_27" openjdk. > > > > { > > "ok" : true, > > "status" : 200, > > "name" : "...", > > "version" : { > > "number" : "0.90.1", > > "snapshot\_build" : false, > > "lucene\_version" : "4.3" > > }, > > "tagline" : "You Know, for Search" > > } > > > > Cluster health: > > { > > "cluster\_name" : "staging\_cluster", > > "status" : "green", > > "timed\_out" : false, > > "number\_of\_nodes" : 3, > > "number\_of\_data\_nodes" : 3, > > "active\_primary\_shards" : 9, > > "active\_shards" : 19, > > "relocating\_shards" : 0, > > "initializing\_shards" : 0, > > "unassigned\_shards" : 0 > > } > > > > -- > > 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). > > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [July 19, 2013, 8:08pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/4 "2013-07-19T20:08:59Z")
Well [http://elasticsearch-users.115913.n3.nabble.com/Best-java-to-run-ElasticSearch-td4030260.html](http://elasticsearch-users.115913.n3.nabble.com/Best-java-to-run-ElasticSearch-td4030260.html) indicates you should use the one that works! Personally, I am currently on ES 0.90.0 (not .1) and on Oracle Java 6 (latest versions for Mac, Linux, and Solaris x86). But that's anecdotal evidence, not scientific! Brian On Friday, July 19, 2013 3:45:27 PM UTC-4, Dave Konopka wrote: > We've been running OpenJDK for a while without issues. This only started > happening after the upgrade to 0.90.1. > > Is Oracle Java recommended officially over OpenJDK? > > On Fri, Jul 19, 2013 at 12:35 PM, InquiringMind \<[brian....@gmail.com](mailto:brian....@gmail.com)\ > > > wrote: > > > Oracle (formerly Sun) Java is good. Java 6 works for me (political > > reasons keep me from going to Java 7 at the moment), though java 7 is > > recommended. > > > > OpenJDK is not good. It's "exactly the same as Oracle Java, except that > > it's different". And it's those little differences that will cripple your > > application with strange and unpredictable failures. > > > > On Friday, July 19, 2013 11:51:23 AM UTC-4, Dave Konopka wrote: > > > > > We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one > > > of the nodes is intermittently showing messages like these in the logs: > > > > > > [transport.netty] Message not fully read (response) for [12652] handler > > > org.elasticsearch.action.suppo **rt.master.TransportMasterNodeO** > > > perationAction$4@53854b5f, error [true], resetting > > > > > > I saw an earlier thread that this could be an issue with 0.90.0 that was > > > fixed in 0.90.1. Odd though that it seems to have started for us with 0.90.1 > > > > > > Anyone have any thoughts or suggestions? > > > > > > The nodes are all running java version "1.6.0\_27" openjdk. > > > > > > { > > > "ok" : true, > > > "status" : 200, > > > "name" : "...", > > > "version" : { > > > "number" : "0.90.1", > > > "snapshot\_build" : false, > > > "lucene\_version" : "4.3" > > > }, > > > "tagline" : "You Know, for Search" > > > } > > > > > > Cluster health: > > > { > > > "cluster\_name" : "staging\_cluster", > > > "status" : "green", > > > "timed\_out" : false, > > > "number\_of\_nodes" : 3, > > > "number\_of\_data\_nodes" : 3, > > > "active\_primary\_shards" : 9, > > > "active\_shards" : 19, > > > "relocating\_shards" : 0, > > > "initializing\_shards" : 0, > > > "unassigned\_shards" : 0 > > > } > > > > > > -- > > > 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) \. > > > 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\ **Post date:** [July 19, 2013, 8:46pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/5 "2013-07-19T20:46:36Z")
Dave Konopka wrote: > We recently updated a three node cluster from 0.90.0 to > 0.90.1. Now one of the nodes is intermittently showing messages > like these in the logs: > > [transport.netty] Message not fully read (response) for [12652] > handler org. > elasticsearch.action.support.master. > TransportMasterNodeOperationAction$4@53854b5f, error [true], > resetting You have some node that's likely still on 0.90.0. Try running this on one of your nodes and make sure each line is the same. ``` curl -s users.elasticsearch.org/drewr/es-version.sh | sh ``` Drew -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Dave\_Konopka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dave_konopka/32/2235_2.png) [@Dave\_Konopka](https://discuss.elastic.co/u/Dave_Konopka)\ **Post date:** [July 22, 2013, 12:29pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/6 "2013-07-22T12:29:44Z")
Hi Drew, All nodes are reporting 0.9.1 and the same Java version: 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] Dave On Fri, Jul 19, 2013 at 4:46 PM, Drew Raines [aaraines@gmail.com](mailto:aaraines@gmail.com) wrote: > Dave Konopka wrote: > > We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one > > > of the nodes is intermittently showing messages like these in the logs: > > > > [transport.netty] Message not fully read (response) for [12652] handler > > org. > > elasticsearch.action.support.**master. > > TransportMasterNodeOperationAc**tion$4@53854b5f, error [true], resetting > > You have some node that's likely still on 0.90.0. Try running this on one > of your nodes and make sure each line is the same. > > curl -s [users.elasticsearch.org/drewr/\*\*es-version.sh](http://users.elasticsearch.org/drewr/**es-version.sh)[http://users.elasticsearch.org/drewr/es-version.sh](http://users.elasticsearch.org/drewr/es-version.sh)| sh > > Drew -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Dave\_Konopka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dave_konopka/32/2235_2.png) [@Dave\_Konopka](https://discuss.elastic.co/u/Dave_Konopka)\ **Post date:** [July 22, 2013, 3:52pm UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/7 "2013-07-22T15:52:44Z")
java -version revealed that IcedTea6 version was different on one node. I updated that node (which rebuilt the jre libs) and things seem to be running smoothly again. On Mon, Jul 22, 2013 at 8:29 AM, Dave Konopka [dave.konopka@gmail.com](mailto:dave.konopka@gmail.com)wrote: > Hi Drew, > > All nodes are reporting 0.9.1 and the same Java version: > 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] > 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] > 0.90.1 OpenJDK 64-Bit Server VM 1.6.0\_27 inet[/0.0.0.0:9300] > > Dave > > On Fri, Jul 19, 2013 at 4:46 PM, Drew Raines [aaraines@gmail.com](mailto:aaraines@gmail.com) wrote: > > > Dave Konopka wrote: > > > > We recently updated a three node cluster from 0.90.0 to 0.90.1. Now one > > > > > of the nodes is intermittently showing messages like these in the logs: > > > > > > [transport.netty] Message not fully read (response) for [12652] handler > > > org. > > > elasticsearch.action.support.**master. > > > TransportMasterNodeOperationAc**tion$4@53854b5f, error [true], resetting > > > > You have some node that's likely still on 0.90.0. Try running this on > > one of your nodes and make sure each line is the same. > > > > curl -s [users.elasticsearch.org/drewr/\*\*es-version.sh](http://users.elasticsearch.org/drewr/**es-version.sh)[http://users.elasticsearch.org/drewr/es-version.sh](http://users.elasticsearch.org/drewr/es-version.sh)| sh > > > > Drew -- 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). 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, 2:25am UTC](https://discuss.elastic.co/t/message-not-fully-read-response-after-upgrading-0-90-0-to-0-90-1/12860/8 "2017-07-06T02:25:11Z")