# Bug in elasticsearch 5

**URL:** <https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436>\
**Category:** Elasticsearch\
**Created:** [February 17, 2017, 6:07am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436 "2017-02-17T06:07:43Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kamaljit\_Pati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamaljit_pati/32/13731_2.png) [@Kamaljit\_Pati](https://discuss.elastic.co/u/Kamaljit_Pati)\
**Post date:** [February 17, 2017, 6:07am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/1 "2017-02-17T06:07:43Z")

</div>

Hi All,  
I am going to update elasticsearch 2.3.3 to 5.2.0 in my organization. But 1 bug I noticed which was before in elasticsearch 2 also that if i run a script which continuously pushes data to elasticsearch without any sleep or anything. Then within 3 minutes i am observing that :

curl: (7) Failed to connect to ::1: Cannot assign requested address  
curl: (7) Failed to connect to ::1: Cannot assign requested address  
curl: (7) Failed to connect to ::1: Cannot assign requested address  
curl: (7) Failed to connect to ::1: Cannot assign requested address  
curl: (7) Failed to connect to ::1: Cannot assign requested address

messages are coming. after a second or 2, again datas are successfully pushed. Within that fraction of time datas are being lost. Please reply me why it is happening??

---

<div class="post-metadata">

**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 17, 2017, 6:10am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/2 "2017-02-17T06:10:34Z")

</div>

What does your script actually do?

---

<div class="post-metadata">

**Author:** ![Kamaljit\_Pati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamaljit_pati/32/13731_2.png) [@Kamaljit\_Pati](https://discuss.elastic.co/u/Kamaljit_Pati)\
**Post date:** [February 17, 2017, 6:13am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/3 "2017-02-17T06:13:50Z")

</div>

This is my script :  
#! /usr/bin/sh

while [1]  
do  
curl 'localhost:9200/movies/movie/'$i'' -d'{"name":"kamaljit"}'  
done

Only it is pushing data without any sleep.

---

<div class="post-metadata">

**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 17, 2017, 6:37am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/4 "2017-02-17T06:37:55Z")

</div>

Anything in logs?

---

<div class="post-metadata">

**Author:** ![Kamaljit\_Pati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamaljit_pati/32/13731_2.png) [@Kamaljit\_Pati](https://discuss.elastic.co/u/Kamaljit_Pati)\
**Post date:** [February 17, 2017, 9:07am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/5 "2017-02-17T09:07:29Z")

</div>

Hi David,  
At that time root logger was in debug mode. In that everything was normal. Like i said that "Cannot assign requested address " situation persists for at least a second or 2 and then again it was successful in inserting the values.

But if need the logs which log you want normal mode logs or debug mode logs. I will again reproduce this and send you the logs.

---

<div class="post-metadata">

**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 17, 2017, 9:25am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/6 "2017-02-17T09:25:25Z")

</div>

Normal logs would be fine.

I wonder also if you can use x-pack to monitor a bit what is happening in your cluster.  
May be you are running out of some resources?

Note that the right way to send a lot of data to elasticsearch is by using bulk but I guess you are trying to overload here elasticsearch to run some "performance tests".

If so, I'd encourage you to look at Rally project: [https://github.com/elastic/rally](https://github.com/elastic/rally)

---

<div class="post-metadata">

**Author:** ![Kamaljit\_Pati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamaljit_pati/32/13731_2.png) [@Kamaljit\_Pati](https://discuss.elastic.co/u/Kamaljit_Pati)\
**Post date:** [February 17, 2017, 11:09am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/7 "2017-02-17T11:09:21Z")

</div>

Hi david,  
you were saying right. When i gave more heap space this situation is not coming, i observed for atleast 7 mins. Is there any direct impact of heap space on this??

And yaa i was doing some performance testing. I need to know how it is behaving under heavy load.

And i think X-pack is not free. So we are not using it only. Thanks David for your input.

Regards  
Kamaljit

---

<div class="post-metadata">

**Author:** ![Kamaljit\_Pati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamaljit_pati/32/13731_2.png) [@Kamaljit\_Pati](https://discuss.elastic.co/u/Kamaljit_Pati)\
**Post date:** [February 17, 2017, 11:20am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/8 "2017-02-17T11:20:54Z")

</div>

Again in another server i gave 16GB as heap size, here also this problem "Failed to connect to ::1: Cannot assign requested address" is coming. May be you are right, bulk is the procedure i should go for.

But in between please check what is the cause for it to happen.  
I am testing in one server cluster(just for testing). It has 32 processor cores and 132 GB RAM. I gave 16 GB as heap space. If you can point me in the right direction, then it will be great use.

---

<div class="post-metadata">

**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 17, 2017, 11:26am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/9 "2017-02-17T11:26:10Z")

</div>

> [@Kamaljit\_Pati](#):
>
> And i think X-pack is not free

There is a free license here [Subscriptions | Elastic Stack Products & Support | Elastic](https://www.elastic.co/subscriptions)  
It will give you access to some features for free like cluster monitoring.

---

<div class="post-metadata">

**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 17, 2017, 11:26am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/10 "2017-02-17T11:26:52Z")

</div>

132Gb of RAM or 32Gb of RAM?

---

<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:** [March 17, 2017, 11:27am UTC](https://discuss.elastic.co/t/bug-in-elasticsearch-5/75436/11 "2017-03-17T11:27:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
