Zone awareness during index reallocation from hot node to warm node


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?

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