# Elasticsearch upgrade from 0.19.2 to higher 0.19.x because of Netty?

**URL:** <https://discuss.elastic.co/t/elasticsearch-upgrade-from-0-19-2-to-higher-0-19-x-because-of-netty/7803>\
**Category:** Elasticsearch\
**Created:** [May 22, 2012, 7:42am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-0-19-2-to-higher-0-19-x-because-of-netty/7803 "2012-05-22T07:42:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 22, 2012, 7:42am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-0-19-2-to-higher-0-19-x-because-of-netty/7803/1 "2012-05-22T07:42:17Z")

</div>

Hi,

We are running 0.19.2 ES in production which AFAIK uses Netty 3.3.1.Final.  
In newer ES releases the Netty has been upgraded to Netty 3.4.1.Final. I  
gave Netty release notes ([http://netty.io/blog/](http://netty.io/blog/)) a quick look and I can see  
bunch of bugfixes between 3.3.1.Final and 3.4.1.Final (are any of them  
really serious?). Is there any reason to consider ES upgrade from 0.19.2 to  
higher version just because of Netty upgrade? Does anybody run into any  
issues because of the Netty 3.3.1.Final?

Regards,  
Lukas

---

<div class="post-metadata">

**Author:** ![Andy\_Wick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andy_wick/32/44017_2.png) [@Andy\_Wick](https://discuss.elastic.co/u/Andy_Wick)\
**Post date:** [May 22, 2012, 4:57pm UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-0-19-2-to-higher-0-19-x-because-of-netty/7803/2 "2012-05-22T16:57:08Z")

</div>

Not sure if a fix in netty or elasticsearch, but upgrading from 0.19.3 to  
0.19.4 fixed an issue I was having with the REST interface not always  
responding or closing the socket when I had a index operation that caused  
an exception. So I would end up with sockets that weren't handling load  
until they timed out.

Thanks,  
Andy

---

<div class="post-metadata">

**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:27am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-0-19-2-to-higher-0-19-x-because-of-netty/7803/3 "2017-07-06T03:27:38Z")

</div>

Closed on July 6, 2017, 3:27am UTC