# Rack Awarness and Node Aware

**URL:** <https://discuss.elastic.co/t/rack-awarness-and-node-aware/339786>\
**Category:** Elasticsearch\
**Created:** [August 1, 2023, 11:00am UTC](https://discuss.elastic.co/t/rack-awarness-and-node-aware/339786 "2023-08-01T11:00:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mannoj87](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@mannoj87](https://discuss.elastic.co/u/mannoj87)\
**Post date:** [August 1, 2023, 11:00am UTC](https://discuss.elastic.co/t/rack-awarness-and-node-aware/339786/1 "2023-08-01T11:00:23Z")

</div>

I'm in 7.17.7 ES.

I have 6BareMetal(BM), each BM will have 4VirtualMachines(VM), each VM's having ES service running and all 5BM are in 3 Physical Racks.

Reason: I dont want Primary and Replica to reside on same BM as well as physically if a RACK is down it shud still have NO dataloss.

So my rack awarness setting will look like.

```auto
node.attr.zone: ${ZONE}
cluster.routing.allocation.awareness.attributes: BM_ID,RACK_ID

```

Will this work?

---

<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:** [August 29, 2023, 11:00am UTC](https://discuss.elastic.co/t/rack-awarness-and-node-aware/339786/2 "2023-08-29T11:00:38Z")

</div>

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