# Forced-awareness in Elastic 8.0.1

**URL:** <https://discuss.elastic.co/t/forced-awareness-in-elastic-8-0-1/301738>\
**Category:** Elasticsearch\
**Created:** [April 6, 2022, 10:25am UTC](https://discuss.elastic.co/t/forced-awareness-in-elastic-8-0-1/301738 "2022-04-06T10:25:07Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![INS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ins/32/92827_2.png) [@INS](https://discuss.elastic.co/u/INS)\
**Post date:** [April 6, 2022, 7:43pm UTC](https://discuss.elastic.co/t/forced-awareness-in-elastic-8-0-1/301738/7 "2022-04-06T19:43:42Z")

</div>

I would also like to bring back the question asked when this case [ES awareness zones/racks](https://discuss.elastic.co/t/es-awareness-zones-racks/116578)

And I am not sure what is the difference between this:  
e.g  
node.rack\_id: rack\_1  
cluster.routing.allocation.awareness.attributes: rack\_id

or  
node.zone: zone1  
cluster.routing.allocation.awareness.attributes: zone

Do they serve the same purpose?

1. cluster.routing.allocation.awareness.attributes: rack\_id,zone  
How does this work?
2. for forced awareness:  
cluster.routing.allocation.awareness.force.zone.values: zone1,zone2

I can see how this works, but is this applicable to only "zones"?  
or you can do:  
cluster.routing.allocation.awareness.force.rack\_id.values: rack\_1,rack\_2?

---

_[View the full topic](https://discuss.elastic.co/t/forced-awareness-in-elastic-8-0-1/301738)._