# Added a new machine - it gets no shards :(

**URL:** <https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407>\
**Category:** Elasticsearch\
**Created:** [July 13, 2016, 1:04pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407 "2016-07-13T13:04:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aviad\_Sharfshtein](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@Aviad\_Sharfshtein](https://discuss.elastic.co/u/Aviad_Sharfshtein)\
**Post date:** [July 13, 2016, 1:04pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407/1 "2016-07-13T13:04:48Z")

</div>

Hi,

I have an old 1.0.0 ES cluster in production, just added a new machine to the cluster and it changed its state to 'Yellow' as expected.

however, it seems like it is stuck, and no shards are being allocated to it.  
running: :9200/\_cluster/health?pretty=true yields the following:

{  
"cluster\_name" : "mycluster",  
"status" : "yellow",  
"timed\_out" : false,  
"number\_of\_nodes" : 12,  
"number\_of\_data\_nodes" : 12,  
"active\_primary\_shards" : 230,  
"active\_shards" : 2530,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 230  
}

in the yml we have the following settings:  
index.number\_of\_shards: 1  
index.auto\_expand\_replicas: "0-all"  
#index.number\_of\_replicas: 0

thanks.

---

<div class="post-metadata">

**Author:** ![Aviad\_Sharfshtein](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@Aviad\_Sharfshtein](https://discuss.elastic.co/u/Aviad_Sharfshtein)\
**Post date:** [July 13, 2016, 2:03pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407/2 "2016-07-13T14:03:10Z")

</div>

Ok,  
so i've removed an older machine, and the new machine started replicating immediately.  
is there some kind of limit on the number of replicas?

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [July 13, 2016, 2:23pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407/3 "2016-07-13T14:23:25Z")

</div>

I can't really comment on this one, but this is an old version and newer versions got a lot of fixes, especially around how elasticsearch works as a distributed system, so maybe you should look into upgrading and see if the issue still exists?

---

<div class="post-metadata">

**Author:** ![Aviad\_Sharfshtein](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@Aviad\_Sharfshtein](https://discuss.elastic.co/u/Aviad_Sharfshtein)\
**Post date:** [July 13, 2016, 3:29pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407/4 "2016-07-13T15:29:32Z")

</div>

found it - its awarnes stuff

[https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-awareness.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-awareness.html)

---

<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 5, 2017, 10:35pm UTC](https://discuss.elastic.co/t/added-a-new-machine-it-gets-no-shards/55407/5 "2017-07-05T22:35:56Z")

</div>

Closed on July 5, 2017, 10:35pm UTC