# How to "remove" cluster.routing.allocation.awareness.attributes

**URL:** <https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537>\
**Category:** Elasticsearch\
**Created:** [June 21, 2021, 12:44pm UTC](https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537 "2021-06-21T12:44:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maxime\_Poirier-Journ](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@Maxime\_Poirier-Journ](https://discuss.elastic.co/u/Maxime_Poirier-Journ)\
**Post date:** [June 21, 2021, 12:44pm UTC](https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537/1 "2021-06-21T12:44:38Z")

</div>

Hi there,

We're using Elastic in all our environments from dev, qa to prod. We're currently using cluster.routing.allocation.awareness.attributes on all our clusters based on the attribute "aws\_availability\_zone" meaning that we want our cluster balanced based on the AWS availability zones distribution.

For the example i'll just use us-east-1a, us-east-1b, us-east-1c AZ's. It works as expected but we're reworking the dev, qa stack in other to save AWS cost and in other to do so we decided to do Single AZ cluster. Meaning that all our 3 nodes ( for dev / qa ) would be on the same AZ. I'm kind of new to ES and couldn't figure out a way to properly reallocate shards.

How would you achieve such reallocation? If I don't do anything and just add the nodes in the same AZ because of the awareness i'm stuck with unassigned shards ( yellow cluster ) and of course this is expected. I tried removing the awareness but it seems to be coming back all the time. Or maybe I just need to choose another attribute ( let's say "dev" ) and assign that attribute to other nodes and it would work?

Any insights?

Thank you to help a newbie 😊

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [June 21, 2021, 1:12pm UTC](https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537/2 "2021-06-21T13:12:10Z")

</div>

can you explain what you mean with 'seems to be coming back all the time'? Unless this feature is configured somewhere in index template, that is very unlikely to happen.

---

<div class="post-metadata">

**Author:** ![Maxime\_Poirier-Journ](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@Maxime\_Poirier-Journ](https://discuss.elastic.co/u/Maxime_Poirier-Journ)\
**Post date:** [June 21, 2021, 2:20pm UTC](https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537/3 "2021-06-21T14:20:29Z")

</div>

I fixed it. It was a code 18 from me. Move along 😃

---

<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 19, 2021, 2:20pm UTC](https://discuss.elastic.co/t/how-to-remove-cluster-routing-allocation-awareness-attributes/276537/4 "2021-07-19T14:20:52Z")

</div>

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