# New replica are not getting assigned

**URL:** <https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450>\
**Category:** Elasticsearch\
**Created:** [July 17, 2017, 6:44pm UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450 "2017-07-17T18:44:34Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 19, 2017, 8:52am UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450/21 "2017-07-19T08:52:33Z")

</div>

Removing the forced awareness configuration should help.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 19, 2017, 8:53am UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450/22 "2017-07-19T08:53:58Z")

</div>

> [@Dhara\_Desai](#):
>
> cluster.routing.allocation.awareness.force.availability\_zone.values: zone1, zone2, zone3  
> cluster.routing.allocation.awareness.attributes: availability\_zone

Here it does however seem to be `availability_zone` and not `aws_availability_zone`.

---

<div class="post-metadata">

**Author:** ![Dhara\_Desai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dhara_desai/32/15760_2.png) [@Dhara\_Desai](https://discuss.elastic.co/u/Dhara_Desai)\
**Post date:** [July 19, 2017, 8:56am UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450/23 "2017-07-19T08:56:03Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> Here it does however seem to be availability\_zone and not aws\_availability\_zone.

Right, thats a configuration template that I picked up form our documentation. But I verified with actual settings.

---

<div class="post-metadata">

**Author:** ![Dhara\_Desai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dhara_desai/32/15760_2.png) [@Dhara\_Desai](https://discuss.elastic.co/u/Dhara_Desai)\
**Post date:** [July 24, 2017, 10:29pm UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450/24 "2017-07-24T22:29:26Z")

</div>

I verified that with setting cluster.routing.allocation.awareness.force.aws\_availability\_zone.values: zone1, zone2, zone3, the cluster is assigning 3 replica-shards to each zone. No unassigned shards issue with shards (1 + 8 replica) but beyond that we seem to have nassigned shards problem.

is there any setting that enforces # number of shards per zone ?

FYI, Illl have to conduct some experiments before removing cluster.routing.allocation.awareness.force.aws\_availability\_zone.values: zone1, zone2, zone3 till then I am just curious how is allocation working in our cluster with this setting and 8 replicas pershard per index

---

<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:** [August 21, 2017, 10:30pm UTC](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450/25 "2017-08-21T22:30:11Z")

</div>

Closed on August 21, 2017, 10:30pm UTC

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

[Previous page](https://discuss.elastic.co/t/new-replica-are-not-getting-assigned/93450.md?page=1)
