# Hot / Cold replication shards allocation failed - Elasticsearch 7.4.0

**URL:** <https://discuss.elastic.co/t/hot-cold-replication-shards-allocation-failed-elasticsearch-7-4-0/232586>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [May 14, 2020, 8:48am UTC](https://discuss.elastic.co/t/hot-cold-replication-shards-allocation-failed-elasticsearch-7-4-0/232586 "2020-05-14T08:48:35Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Thomas74](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Thomas74](https://discuss.elastic.co/u/Thomas74)\
**Post date:** [May 14, 2020, 2:09pm UTC](https://discuss.elastic.co/t/hot-cold-replication-shards-allocation-failed-elasticsearch-7-4-0/232586/5 "2020-05-14T14:09:34Z")

</div>

I changed the `elasticsearch.yml` it and it works now !! 🙂

I also saw another answer from you here were you already explain that ^^'

> [@Replica allocation awareness](https://discuss.elastic.co/t/replica-allocation-awareness/197491/13):
>
> I found 1 hot node still with the allocation setting, can I remove it with an API call or do I need a restart? The setting is commented out in the elasticsearch.yml "settings" : { "pidfile" : "/var/run/elasticsearch/elasticsearch.pid", "cluster" : { "name" : "es-cluster", "routing" : { "allocation" : { "awareness" : { "attributes" : "data" } } },

Maybe the cluster API will do this change a day 🙂

Thanks a lot !

---

_[View the full topic](https://discuss.elastic.co/t/hot-cold-replication-shards-allocation-failed-elasticsearch-7-4-0/232586)._