# Zone awareness during index reallocation from hot node to warm node
**URL:** https://discuss.elastic.co/t/zone-awareness-during-index-reallocation-from-hot-node-to-warm-node/91018
**Category:** Elasticsearch
**Created:** [June 27, 2017, 7:16pm UTC](https://discuss.elastic.co/t/zone-awareness-during-index-reallocation-from-hot-node-to-warm-node/91018 "2017-06-27T19:16:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Kamlesh\_Pandey](https://discuss.elastic.co/u/Kamlesh_Pandey)
#### Post date: [June 27, 2017, 7:16pm UTC](https://discuss.elastic.co/t/zone-awareness-during-index-reallocation-from-hot-node-to-warm-node/91018/1 "2017-06-27T19:16:42Z")
Hi,
We have a hot warm architecture for elasticsearch and have a zone awareness also in place for primary and replica shards.
We have observed that during hot \> warm allocation of the index after 2 days, the index gets relocated to different availability zone in the warm node. This transfer to a different availability zone have some performance impact.
How can I make sure that the index goes to warm node in the same availability zone as it was in the hot node so as to get maximum performance during the reallocation?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 25, 2017, 7:17pm UTC](https://discuss.elastic.co/t/zone-awareness-during-index-reallocation-from-hot-node-to-warm-node/91018/2 "2017-07-25T19:17:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.