# StreamCorruptedException after upgrading to 0.20.0RC1 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 5, 2012, 5:08pm UTC](https://discuss.elastic.co/t/streamcorruptedexception-after-upgrading-to-0-20-0rc1/9563 "2012-11-05T17:08:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 5, 2012, 5:08pm UTC](https://discuss.elastic.co/t/streamcorruptedexception-after-upgrading-to-0-20-0rc1/9563/1 "2012-11-05T17:08:54Z")
Upgraded a 12 node cluster from 0.19.2 to 0.20.0RC1. Plugins (head/bigdesk) were reinstalled from scratch, but the service wrapper and config directories are identical from the previous version. The cluster contained two indices built with 0.19.2 No clients are connected (except for the plugins). Reallocation was not disabled before the restart, but the nodes were all stopped and started within seconds of each other. Cluster was originally yellow since the shards were initializing, but it eventually went to green. Logs are quickly filling up with these exceptions: [2012-11-05 09:06:03,419][WARN][transport.netty] [srch-lv108] exception caught on transport layer [[id: 0xb84d3508, /192.168.52.150:40744:\> /192.168.52.158:9300]], closing connection java.io.StreamCorruptedException: invalid internal transport message format at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:27) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:422) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:478) at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.channelDisconnected(FrameDecoder.java:366) ... Cheers, Ivan -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 5, 2012, 5:56pm UTC](https://discuss.elastic.co/t/streamcorruptedexception-after-upgrading-to-0-20-0rc1/9563/2 "2012-11-05T17:56:34Z")
Maybe I should pay more attention to the error messages. The exception listed the servers in question ans showed that one rogue client was still up. Back to testing 0.20 ... On Mon, Nov 5, 2012 at 9:08 AM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Upgraded a 12 node cluster from 0.19.2 to 0.20.0RC1. Plugins > (head/bigdesk) were reinstalled from scratch, but the service wrapper and > config directories are identical from the previous version. The cluster > contained two indices built with 0.19.2 > > No clients are connected (except for the plugins). Reallocation was not > disabled before the restart, but the nodes were all stopped and started > within seconds of each other. Cluster was originally yellow since the > shards were initializing, but it eventually went to green. > > Logs are quickly filling up with these exceptions: > > [2012-11-05 09:06:03,419][WARN][transport.netty] [srch-lv108] > exception caught on transport layer [[id: 0xb84d3508, / > 192.168.52.150:40744 :\> /192.168.52.158:9300]], closing connection > java.io.StreamCorruptedException: invalid internal transport message format > at > org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:27) > at > org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:422) > at > org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:478) > at > org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.channelDisconnected(FrameDecoder.java:366) > ... > > Cheers, > > Ivan -- ---
**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, 3:06am UTC](https://discuss.elastic.co/t/streamcorruptedexception-after-upgrading-to-0-20-0rc1/9563/3 "2017-07-06T03:06:10Z")