# Shards unassigned after datanode addition

**URL:** <https://discuss.elastic.co/t/shards-unassigned-after-datanode-addition/191130>\
**Category:** Elasticsearch\
**Created:** [July 18, 2019, 5:58am UTC](https://discuss.elastic.co/t/shards-unassigned-after-datanode-addition/191130 "2019-07-18T05:58:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [July 18, 2019, 6:41am UTC](https://discuss.elastic.co/t/shards-unassigned-after-datanode-addition/191130/2 "2019-07-18T06:41:37Z")

</div>

The primary was on a node with ID `B2GcZ5KFRG23IMePeJWA4g` a couple of days ago:

> [@viratag26](#):
>
> ```auto
> "unassigned_info": {
> "reason": "NODE_LEFT",
> "at": "2019-07-16T05:01:51.383Z",
> "details": "node_left[B2GcZ5KFRG23IMePeJWA4g]",
> 
> ```

This node no longer has any trace of this shard:

> [@viratag26](#):
>
> ```auto
> {
> "node_id": "B2GcZ5KFRG23IMePeJWA4g",
> "node_name": "dxb-dso01-nec-nfvi2-cmn-nec-celshd01.nfvi.localdomain",
> "transport_address": "172.17.41.145:9300",
> ...
> "store": {
> "found": false
> }
> 
> ```

I think you have done something more destructive than simply adding a node to this cluster, because that would not cause what we're seeing here.

---

_[View the full topic](https://discuss.elastic.co/t/shards-unassigned-after-datanode-addition/191130)._