# Shard allocation awareness implementation in elasticsarch

**URL:** <https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193>\
**Category:** Elasticsearch\
**Created:** [April 25, 2021, 3:20pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193 "2021-04-25T15:20:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![722826c085cfc824006d](https://avatars.discourse-cdn.com/v4/letter/7/4bbf92/32.png) [@722826c085cfc824006d](https://discuss.elastic.co/u/722826c085cfc824006d)\
**Post date:** [April 25, 2021, 3:20pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193/1 "2021-04-25T15:20:32Z")

</div>

we are using open source elasticsearch 5.6.10 from last 2 years in AWS cloud, but didn't implement shard allocation awareness in the clusters. Since the lack of shard allocation of awareness, the shards are distributed in the same zone.

Currently we are planning to implement the shard zone awareness attributes in the elasticsearch config yaml file. we have around 20 nodes in each cluster, distributed across all availability zones equally.

Please let us know the process for shard awareness migration without having any downtime?

---

<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:** [April 25, 2021, 6:02pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193/2 "2021-04-25T18:02:50Z")

</div>

> [@722826c085cfc824006d](#):
>
> we are using open source elasticsearch 5.6.10 from last 2 years

This version is very old, it went [EOL](https://www.elastic.co/support/eol) more than 2 years ago, perhaps even before you _started_ using it? You should upgrade as a matter of urgency.

> [@722826c085cfc824006d](#):
>
> Please let us know the process for shard awareness migration without having any downtime?

Do a rolling restart to set the node attributes on each node, and then do another one to set `cluster.routing.allocation.awareness.attributes`.

---

<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:** [April 26, 2021, 5:16am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193/3 "2021-04-26T05:16:04Z")

</div>

Is this the aws service, or are you running on ec2?

---

<div class="post-metadata">

**Author:** ![722826c085cfc824006d](https://avatars.discourse-cdn.com/v4/letter/7/4bbf92/32.png) [@722826c085cfc824006d](https://discuss.elastic.co/u/722826c085cfc824006d)\
**Post date:** [April 26, 2021, 9:55am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193/4 "2021-04-26T09:55:25Z")

</div>

This is opensource ES, it is running on VM's.

---

<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:** [May 24, 2021, 9:56am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-implementation-in-elasticsarch/271193/5 "2021-05-24T09:56:10Z")

</div>

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