# Replica allocation awareness

**URL:** <https://discuss.elastic.co/t/replica-allocation-awareness/197491>\
**Category:** Elasticsearch\
**Created:** [August 30, 2019, 10:25am UTC](https://discuss.elastic.co/t/replica-allocation-awareness/197491 "2019-08-30T10:25:20Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![JacovanZyl](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JacovanZyl](https://discuss.elastic.co/u/JacovanZyl)\
**Post date:** [September 2, 2019, 9:52am UTC](https://discuss.elastic.co/t/replica-allocation-awareness/197491/13 "2019-09-02T09:52:30Z")

</div>

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"
          }
        }
      },
```

---

_[View the full topic](https://discuss.elastic.co/t/replica-allocation-awareness/197491)._