# Hot, warm, cold tiering with availability zones

**URL:** <https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [August 22, 2024, 10:04pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413 "2024-08-22T22:04:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jelliott1](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jelliott1](https://discuss.elastic.co/u/jelliott1)\
**Post date:** [August 22, 2024, 10:04pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/1 "2024-08-22T22:04:05Z")

</div>

Hello,  
I'm trying to understand ILM behavior with ECE availability zones.  
If I distribute a cluster across 2 or more availability zones, will a replica on zone 2 from a primary on zone 1 eventually move from the hot to warm tier on zone 2, when the ILM condition is reached, if the policy has been created?

---

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [August 23, 2024, 4:34am UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/2 "2024-08-23T04:34:48Z")

</div>

> [@jelliott1](#):
>
> I'm trying to understand ILM behavior with ECE availability zones.  
> If I distribute a cluster across 2 or more availability zones, will a replica on zone 2 from a primary on zone 1 eventually move from the hot to warm tier on zone 2, when the ILM condition is reached, if the policy has been created?

Hi,

In our environment we have 3 Zones (3 HOT nodes on each zone & 2 WARM nodes on 2 zone).  
So as per my understanding it is not like Shards move from Hot to Warm tier zone wise, it can be any zone as it depends on the number of Shards on each node. It divides equally on the 3/2 nodes WARM in our scenario.

Thanks!

---

<div class="post-metadata">

**Author:** ![jelliott1](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jelliott1](https://discuss.elastic.co/u/jelliott1)\
**Post date:** [August 23, 2024, 1:09pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/3 "2024-08-23T13:09:13Z")

</div>

Hello,  
Thank you very much for your reply! Just to be sure that I understand:  
If I have a primary shard on zone 1 with a replica shard on zone 2, the replica shard on zone 2 can be moved to the warm tier on zone 2 once ILM conditions are met. Am I understanding that correctly?  
Thank you again!

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 23, 2024, 2:39pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/4 "2024-08-23T14:39:27Z")

</div>

Hi @jelliott1

Simply Put, with default routing, there is no guarantee that a primary or replica shard will stay in the same zone as it moves between data tiers.

The shard may or may not end up in the same zone.

Can I ask what your concern is or what you are trying to accomplish?

---

<div class="post-metadata">

**Author:** ![jelliott1](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jelliott1](https://discuss.elastic.co/u/jelliott1)\
**Post date:** [August 23, 2024, 2:54pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/5 "2024-08-23T14:54:36Z")

</div>

Hi @stephenb  
Thank you for your quick reply to my question!  
I'm attempting to size storage for the warm tier in a 2-zone ECE cluster. The third zone is being used as a tiebreaker. I need to make sure the warm tier has enough storage to endure a zone failure. My first thought was to size the warm tier for the replicas from the other site plus hot primaries from data being ingested at each zone. That's assuming incoming data is balanced across both zones.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 23, 2024, 3:50pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/6 "2024-08-23T15:50:34Z")

</div>

> [@jelliott1](#):
>
> I need to make sure the warm tier has enough storage to endure a zone failure. My first thought was to size the warm tier for the replicas from the other site plus hot primaries from data being ingested at each zone.

Sorry, I am not clear about what you are trying to solve.

Warm needs to have space for primary and replicas...

Not sure what you mean by other sites etc...

You DO need to use routing if you have multiple warm nodes in each zone to ensure the primary and replica are in different zones... I \ ***think** this happens automatically if you have set up ECE properly across AZs

BTW you have ECE so by definition, you have Support so you can ask that.

---

<div class="post-metadata">

**Author:** ![jelliott1](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jelliott1](https://discuss.elastic.co/u/jelliott1)\
**Post date:** [August 23, 2024, 4:56pm UTC](https://discuss.elastic.co/t/hot-warm-cold-tiering-with-availability-zones/365413/7 "2024-08-23T16:56:46Z")

</div>

@stephenb  
Thanks for clarifying that!
