# What is the work-around before this is fixed....Sending a HTTP request to TCP port during recovery results in OutOfMemoryError in Netty Issue#1955

**URL:** <https://discuss.elastic.co/t/what-is-the-work-around-before-this-is-fixed-sending-a-http-request-to-tcp-port-during-recovery-results-in-outofmemoryerror-in-netty-issue-1955/7852>\
**Category:** Elasticsearch\
**Created:** [May 24, 2012, 9:39pm UTC](https://discuss.elastic.co/t/what-is-the-work-around-before-this-is-fixed-sending-a-http-request-to-tcp-port-during-recovery-results-in-outofmemoryerror-in-netty-issue-1955/7852 "2012-05-24T21:39:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchgirl](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@searchgirl](https://discuss.elastic.co/u/searchgirl)\
**Post date:** [May 24, 2012, 9:39pm UTC](https://discuss.elastic.co/t/what-is-the-work-around-before-this-is-fixed-sending-a-http-request-to-tcp-port-during-recovery-results-in-outofmemoryerror-in-netty-issue-1955/7852/1 "2012-05-24T21:39:12Z")

</div>

I am using 0.19.3 and while index (not bulk) a large dataset, I run  
into this problem with out-of-memory error.

This has been documented here: [https://github.com/elasticsearch/elasticsearch/issues/1955](https://github.com/elasticsearch/elasticsearch/issues/1955)

I am still a newbie to this and is in the process of evaluating  
ElasticSearch. This is kind of a blocker for me.

I am just wondering if there is a work-around in the meantime? Or  
when will a patch be available?

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 25, 2012, 11:10pm UTC](https://discuss.elastic.co/t/what-is-the-work-around-before-this-is-fixed-sending-a-http-request-to-tcp-port-during-recovery-results-in-outofmemoryerror-in-netty-issue-1955/7852/2 "2012-05-25T23:10:11Z")

</div>

I answered on the issue. Just note that you send HTTP requests to port  
9200, not 9300, 9300 is for internal communication protocol.

On Thu, May 24, 2012 at 11:39 PM, Helen Poon [helenchenpoon@gmail.com](mailto:helenchenpoon@gmail.com)wrote:

> I am using 0.19.3 and while index (not bulk) a large dataset, I run  
> into this problem with out-of-memory error.
> 
> This has been documented here:  
> [Sending a HTTP request to TCP port during recovery results in OutOfMemoryError in Netty · Issue #1955 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1955)
> 
> I am still a newbie to this and is in the process of evaluating  
> Elasticsearch. This is kind of a blocker for me.
> 
> I am just wondering if there is a work-around in the meantime? Or  
> when will a patch be available?

---

<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:26am UTC](https://discuss.elastic.co/t/what-is-the-work-around-before-this-is-fixed-sending-a-http-request-to-tcp-port-during-recovery-results-in-outofmemoryerror-in-netty-issue-1955/7852/3 "2017-07-06T03:26:53Z")

</div>