# ILM has rolled over indices way over the limits

**URL:** <https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [December 5, 2019, 4:57am UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620 "2019-12-05T04:57:17Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\
**Post date:** [December 5, 2019, 4:57am UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/1 "2019-12-05T04:57:17Z")

</div>

I setup a policy (ILM) for an index to roll over to a new index when: **maximum index size = 50GB or maximum age = 1d**

Right now, I have 3 indexes which were created by the policy above, but their size is way above 50GB.

```
gcp_vpc_flow-000003 green open 4 1 73648356 121.1gb (current index)
shrink-gcp_vpc_flow-000002 green open 1 1 73856698 95.7gb (rolled over)
shrink-gcp_vpc_flow-000001 green open 1 1 73822098 95.8gb (rolled over)

```

Why are rolled over indexes over 50GB in size?

---

<div class="post-metadata">

**Author:** ![amhulli](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@amhulli](https://discuss.elastic.co/u/amhulli)\
**Post date:** [December 16, 2019, 12:38am UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/2 "2019-12-16T00:38:30Z")

</div>

I'm having the same issue (almost). I have the same policy applied but my current index won't rollover at all (unless I manually intervene). Current index is at 80gb. Sorry for jumping in on your question but I think the source of my issue might be similar and as such following it might produce results for me too.

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [December 16, 2019, 1:50am UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/3 "2019-12-16T01:50:01Z")

</div>

The size is for the primary copy, if you have 1 replica, then it will appear to roll over at 100G. If they are over that limit, check Kibana Index Management for ILM errors.

---

<div class="post-metadata">

**Author:** ![VietCong](https://avatars.discourse-cdn.com/v4/letter/v/e47774/32.png) [@VietCong](https://discuss.elastic.co/u/VietCong)\
**Post date:** [December 16, 2019, 4:26am UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/4 "2019-12-16T04:26:16Z")

</div>

Agreed with Regenl. I believe the size you see includes both replica and primary shard. I am a little bit confused by the index name though. It says shrink in front. I am not sure if they are indices being rolled over by ILM. Are you sure the roll over working at all?

---

<div class="post-metadata">

**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\
**Post date:** [December 16, 2019, 5:56pm UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/5 "2019-12-16T17:56:10Z")

</div>

Great, this totally makes sense now. It seems that I have two shards 50GB each: primary and replica, and that's why I've been seeing ~100GB on the shrink indices.

---

<div class="post-metadata">

**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\
**Post date:** [December 16, 2019, 5:56pm UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/6 "2019-12-16T17:56:34Z")

</div>

No errors in Kibana.

---

<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:** [December 30, 2019, 5:56pm UTC](https://discuss.elastic.co/t/ilm-has-rolled-over-indices-way-over-the-limits/210620/7 "2019-12-30T17:56:35Z")

</div>

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