# Hot-Warm-Cold Log Transistion

**URL:** https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [September 7, 2020, 12:53am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688 "2020-09-07T00:53:42Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![vishakh](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@vishakh](https://discuss.elastic.co/u/vishakh)
#### Post date: [September 7, 2020, 12:53am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/1 "2020-09-07T00:53:42Z")

</div>

Objective: Implement Hot-Warm-Cold Architecture  
At first when ingested from beats, data should be only be ingested and spread across only on Hot nodes. After 30-days logs moved to warm and then after 60 days to cold  
(ELK-Stack Version: 7.8.0)

On the hot nodes, I did add the config as

```auto
cluster.routing.allocation.awareness.attributes: index_state
node.attr.index_state: hot

```

and on warm nodes, I added as the config as:

```auto
cluster.routing.allocation.awareness.attributes: index_state
node.attr.index_state: warm

```

But while observing, I seriously noticed that all newly ingested logs-shards got shared/stored on warm node as-well. As soon as I introduced the wam node into the cluster all the shards were spread across which defeats the purpose.

Can anyone please guide/help me on this issue

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 7, 2020, 12:56am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/2 "2020-09-07T00:56:14Z")

</div>

What does your ILM policy look like?

---

<div class="post-metadata">

### Author: ![Camilo\_Diaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/camilo_diaz/32/46512_2.png) [@Camilo\_Diaz](https://discuss.elastic.co/u/Camilo_Diaz)
#### Post date: [September 7, 2020, 4:46am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/3 "2020-09-07T04:46:34Z")

</div>

I had the same exact problem. The fix for my was to set 'node.data: false' on the warm node, however I am still having problems to move the data to my warm node after X days.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 7, 2020, 4:57am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/4 "2020-09-07T04:57:35Z")

</div>

> [@Camilo\_Diaz](#):
>
> The fix for my was to set 'node.data: false' on the warm node

That is not a fix, it just means your warm node will not store any indexed data.

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 7, 2020, 5:06am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/5 "2020-09-07T05:06:50Z")

</div>

Have you added the required index setting to your index templates?

---

<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: [October 5, 2020, 5:06am UTC](https://discuss.elastic.co/t/hot-warm-cold-log-transistion/247688/6 "2020-10-05T05:06:53Z")

</div>

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