# Elasticsearch ILM rollover from hot to warm phase not happening even when the condition for rollover is met

**URL:** https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [August 1, 2019, 2:08am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235 "2019-08-01T02:08:05Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![ElkNovice](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElkNovice](https://discuss.elastic.co/u/ElkNovice)
#### Post date: [August 1, 2019, 2:08am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/1 "2019-08-01T02:08:05Z")

</div>

Elasticsearch version 7.1

I have created ILM policy as per which if the index grows more than 50 GB in size or is more than 15days old the index should rollover to warm phase. In my env, this is not happening consistently. I see few old indexes which have grown to more than 100-200GB and then rollover happened. Looking at that I changed the "indices . lifecycle . poll\_interval": "1m", it has been a few days since I changed the poll\_interval to 1m, yet I see indexes about 80GB in size in Hot phase. I want to understand why the rollover isn't happening when 50 GB size is reached?

ILM:  
{  
"policy": {  
"phases": {  
"hot": {  
"min\_age": "0ms",  
"actions": {  
"rollover": {  
"max\_age": "15d",  
"max\_size": "50gb"  
},  
"set\_priority": {  
"priority": 5000  
}  
}  
},  
"warm": {  
"min\_age": "0ms",  
"actions": {  
"allocate": {  
"number\_of\_replicas": 1,  
"include": {},  
"exclude": {},  
"require": {  
"data": "warm"  
}  
},  
"forcemerge": {  
"max\_num\_segments": 1  
},  
"set\_priority": {  
"priority": 2000  
}  
}  
},  
"delete": {  
"min\_age": "75d",  
"actions": {  
"delete": {}  
}  
}  
}  
}  
}

![image](https://us1.discourse-cdn.com/elastic/original/3X/d/b/db21f16b2a344ddbce947d04bb768fcef4993a6e.png)

---

<div class="post-metadata">

### Author: ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)
#### Post date: [August 1, 2019, 3:54am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/2 "2019-08-01T03:54:03Z")

</div>

Hi ElkNovice,

Can you provide the output of the following:

```auto
GET /<your-index>/_ilm/explain?human

```

That will hopefully shed some light on why it is not rolling over.

---

<div class="post-metadata">

### Author: ![ElkNovice](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElkNovice](https://discuss.elastic.co/u/ElkNovice)
#### Post date: [August 1, 2019, 3:57am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/3 "2019-08-01T03:57:29Z")

</div>

Output of "GET /myindex/\_ilm/explain?human"  
{  
"indices" : {  
"logs-2019.07.28-000001" : {  
"index" : "logs-2019.07.28-000001",  
"managed" : true,  
"policy" : "ilm-15days50gbHot-90daysDelete",  
"lifecycle\_date" : "2019-07-28T03:37:20.642Z",  
"lifecycle\_date\_millis" : 1564285040642,  
"phase" : "hot",  
"phase\_time" : "2019-07-28T03:37:26.102Z",  
"phase\_time\_millis" : 1564285046102,  
"action" : "rollover",  
"action\_time" : "2019-07-28T03:43:10.006Z",  
"action\_time\_millis" : 1564285390006,  
"step" : "check-rollover-ready",  
"step\_time" : "2019-07-28T03:43:10.006Z",  
"step\_time\_millis" : 1564285390006,  
"phase\_execution" : {  
"policy" : "ilm-15days50gbHot-90daysDelete",  
"phase\_definition" : {  
"min\_age" : "0ms",  
"actions" : {  
"rollover" : {  
"max\_size" : "50gb",  
"max\_age" : "15d"  
},  
"set\_priority" : {  
"priority" : 5000  
}  
}  
},  
"version" : 2,  
"modified\_date" : "2019-06-11T05:23:23.374Z",  
"modified\_date\_in\_millis" : 1560230603374  
}  
}  
}  
}

---

<div class="post-metadata">

### Author: ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)
#### Post date: [August 1, 2019, 4:00am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/4 "2019-08-01T04:00:13Z")

</div>

Okay the age has definitely not been met (since the index is only a couple of days old), what is the output of

```auto
GET /_cat/shards/<your-index>?v

```

That should show the size of the shards for it

---

<div class="post-metadata">

### Author: ![ElkNovice](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElkNovice](https://discuss.elastic.co/u/ElkNovice)
#### Post date: [August 1, 2019, 4:01am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/5 "2019-08-01T04:01:18Z")

</div>

index shard prirep state docs store ip node  
logs-2019.07.28-000001 0 r STARTED 154154419 44.5gb xxx node1\_data\_hot  
logs-2019.07.28-000001 0 p STARTED 154154419 44.5gb xxx node2\_data\_hot

---

<div class="post-metadata">

### Author: ![ElkNovice](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElkNovice](https://discuss.elastic.co/u/ElkNovice)
#### Post date: [August 1, 2019, 4:02am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/6 "2019-08-01T04:02:36Z")

</div>

Is the size in ILM specific to primary shard size?

---

<div class="post-metadata">

### Author: ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)
#### Post date: [August 1, 2019, 4:04am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/7 "2019-08-01T04:04:15Z")

</div>

Yes that's correct, since the primary shard is only 44.55gb, it hasn't hit the 50gb limit, that is why this hasn't rolled over yet.

See: [https://www.elastic.co/guide/en/elasticsearch/reference/7.3/indices-rollover-index.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/indices-rollover-index.html) which mentions: `max_size` The maximum estimated size of the **primary shard** of the index

---

<div class="post-metadata">

### Author: ![ElkNovice](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@ElkNovice](https://discuss.elastic.co/u/ElkNovice)
#### Post date: [August 1, 2019, 4:05am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/8 "2019-08-01T04:05:20Z")

</div>

I overlooked that when reading the documentation, thanks for your help. Will keep an eye on the primary shard size and validate that rollover happens.

---

<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, 2019, 4:05am UTC](https://discuss.elastic.co/t/elasticsearch-ilm-rollover-from-hot-to-warm-phase-not-happening-even-when-the-condition-for-rollover-is-met/193235/9 "2019-08-29T04:05:32Z")

</div>

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