# Ingest node disc usage keeps rising

**URL:** <https://discuss.elastic.co/t/ingest-node-disc-usage-keeps-rising/284431>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [September 16, 2021, 7:36pm UTC](https://discuss.elastic.co/t/ingest-node-disc-usage-keeps-rising/284431 "2021-09-16T19:36:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 16, 2021, 7:47pm UTC](https://discuss.elastic.co/t/ingest-node-disc-usage-keeps-rising/284431/2 "2021-09-16T19:47:00Z")

</div>

Hi @Tadija Welcome to the community and thanks for trying Elastic Cloud.

Thanks for taking the time to explain your case.

Can you please share your ILM Policy?

> [@Tadija](#):
>
> I expected it to be much lower since I've setup ILM to move the data immediately.

This is a bit interesting... ILM does not move data "Immediately" it runs in the background periodically. This is often a bit of a misconception. Here is a little more from a previous post.

> [@ILM doesn't work](https://discuss.elastic.co/t/ilm-doesnt-work/284285/3):
>
> Hi @vp096 Is your use case really about deleting data 15 mins old, or are you just testing? The reason I ask is ILM is not really design to operate on "Minute" Scheduled or Small KB/MB indices is designed to manage large scale indices GB, Hours, Days etc. and for that it works very well. I posted a bit about it [here](https://discuss.elastic.co/t/rollover-goes-beyond-the-condition/207442/2) and another elastician [here](https://discuss.elastic.co/t/lifecycle-policies-dont-work/276218/13)

---

_[View the full topic](https://discuss.elastic.co/t/ingest-node-disc-usage-keeps-rising/284431)._