# Unassigned primary shards. reason:NODE LEFT

**URL:** https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805
**Category:** Elasticsearch
**Created:** [December 13, 2016, 2:40am UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805 "2016-12-13T02:40:03Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![chihccha](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@chihccha](https://discuss.elastic.co/u/chihccha)
#### Post date: [December 13, 2016, 2:40am UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805/1 "2016-12-13T02:40:03Z")

</div>

Hi,

Our ES cluster health is often red due to unassigned primary shards.  
The unassign.reason for this is "NODE\_LEFT" (See details below)  
Does this mean that the node left the cluster while it was being assigned the shard?  
When the node comes back, how come the unassigned shards are not reassigned back to that node automatically?

curl localhost:9201/\_cat/shards?h=index,shard,prirep,state,unassigned.reason,usassigned.for,[unassigned.at](http://unassigned.at) | grep UNASSIGNED

index1 3 p UNASSIGNED NODE\_LEFT 2016-12-12T00:03:36.663Z  
index1 3 r UNASSIGNED INDEX\_CREATED 2016-12-12T00:01:03.944Z  
index1 0 p UNASSIGNED NODE\_LEFT 2016-12-12T00:04:59.915Z  
index1 0 r UNASSIGNED INDEX\_CREATED 2016-12-12T00:01:03.944Z

Thanks,  
Chelsey

---

<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: [December 13, 2016, 2:46am UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805/2 "2016-12-13T02:46:09Z")

</div>

What version are you on?  
Have you checked the logs on the nodes that have left?

---

<div class="post-metadata">

### Author: ![chihccha](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@chihccha](https://discuss.elastic.co/u/chihccha)
#### Post date: [December 13, 2016, 4:50pm UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805/3 "2016-12-13T16:50:09Z")

</div>

I am using version 2.3.3. Yes, I've checked the logs of the node (I have debug turned on), but there is not much information besides the node dropped out of the cluster due to ping timeout, did not see anything regarding the shard.

---

<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: [December 13, 2016, 7:51pm UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805/4 "2016-12-13T19:51:32Z")

</div>

Perhaps if you can post the log with the disconnect and things before and after, we can highlight something?

---

<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: [January 10, 2017, 7:51pm UTC](https://discuss.elastic.co/t/unassigned-primary-shards-reason-node-left/68805/5 "2017-01-10T19:51:54Z")

</div>

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