# Index status as red with 1 unassigned shard

**URL:** <https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [February 7, 2018, 5:09am UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750 "2018-02-07T05:09:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alp1](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@Alp1](https://discuss.elastic.co/u/Alp1)\
**Post date:** [February 7, 2018, 5:09am UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750/1 "2018-02-07T05:09:12Z")

</div>

Hi ,

I am running few rally tracks on our dev environment and i observed whenever i run pmc / nyc\_taxis tracks the index goes into red state after some 5GB of data with 1 unassigned shard error. These tracks have data size \> 20GB.

I am not sure why the index goes in to red state with 1 unassigned shard after 5 GB of data .Logs shows the timeout error. Could you give me some pointers

log shows below error -

urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='_._._,_', port=8089): Read timed out. (read timeout=10)  
2018-02-07 05:03:59,959 PID:14010 elasticsearch WARNING POST http://_._._._:8089/\_bulk [status:N/A request:10.043s]  
Traceback (most recent call last):  
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 387, in \_make\_request  
six.raise\_from(e, None)  
File "", line 2, in raise\_from  
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 383, in \_make\_request  
httplib\_response = conn.getresponse()  
File "/usr/lib/python3.4/http/client.py", line 1208, in getresponse  
response.begin()  
File "/usr/lib/python3.4/http/client.py", line 380, in begin  
version, status, reason = self.\_read\_status()  
File "/usr/lib/python3.4/http/client.py", line 342, in \_read\_status  
line = str(self.fp.readline(\_MAXLINE + 1), "iso-8859-1")  
File "/usr/lib/python3.4/socket.py", line 374, in readinto  
return self.\_sock.recv\_into(b)  
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):  
File "/usr/local/lib/python3.4/dist-packages/elasticsearch/connection/http\_urllib3.py", line 147, in perform\_request  
response = self.pool.urlopen(method, url, body, retries=False, headers=self.headers, \*\*kw)  
File "/usr/local/lib/python3.4/dist-packages/esrally/client.py", line 47, in urlopen  
return self.pool.urlopen(method, url, body=body, retries=retries, headers=headers, \*\*kw)  
File "/usr/local/lib/python3.4/dist-packages/urllib3/connectionpool.py", line 639, in urlopen  
\_stacktrace=sys.exc\_info()[2])  
File "/usr/local/lib/python3.4/dist-packages/urllib3/util/retry.py", line 333, in increment

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [February 7, 2018, 7:29am UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750/2 "2018-02-07T07:29:15Z")

</div>

You can use the [cluster allocation explain API](https://www.elastic.co/blog/red-elasticsearch-cluster-panic-no-longer) to find out why you have unassigned shards.

The Rally error that you are posting is different though:

```auto
urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='..,', port=8089): Read timed out. (read timeout=10)

```

This means that the HTTP request has timed out. The timeout value is 10 seconds and you can set `--client-options="timeout:60"` to increase it to e.g. 60 seconds.

---

<div class="post-metadata">

**Author:** ![Alp1](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@Alp1](https://discuss.elastic.co/u/Alp1)\
**Post date:** [February 7, 2018, 7:33pm UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750/3 "2018-02-07T19:33:38Z")

</div>

Thanks Daniel.  
Cluster allocation explain API is really helpful."Node Left" was the reason for unassigned shard error.

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [February 8, 2018, 7:47am UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750/4 "2018-02-08T07:47:53Z")

</div>

Perfect. Glad that it helped. 🙂

---

<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 8, 2018, 7:47am UTC](https://discuss.elastic.co/t/index-status-as-red-with-1-unassigned-shard/118750/5 "2018-03-08T07:47:55Z")

</div>

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