# Using ILM with mutable data and multiple data tiers

**URL:** <https://discuss.elastic.co/t/using-ilm-with-mutable-data-and-multiple-data-tiers/360485>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [May 29, 2024, 2:59pm UTC](https://discuss.elastic.co/t/using-ilm-with-mutable-data-and-multiple-data-tiers/360485 "2024-05-29T14:59:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aevers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aevers/32/134902_2.png) [@aevers](https://discuss.elastic.co/u/aevers)\
**Post date:** [May 29, 2024, 2:59pm UTC](https://discuss.elastic.co/t/using-ilm-with-mutable-data-and-multiple-data-tiers/360485/1 "2024-05-29T14:59:29Z")

</div>

Hi,

We are experiencing load and cost issues related to mutable data.

This is our situation:

- Every day we receive 30 million documents we need to index
- 29.9 million of these documents are not queried often and can be stored in warm or colder storage
- These documents get **updated** multiple times shortly after insertion
- Sporadically, some can be updated days, if not months after the original insertion
- We are only interested in the latest state of each document

We would like to store these 29.9 million mutable documents in a separate index, which can be gradually moved to colder storage to avoid costs.

Any idea on how we could do this?

Kind regards,  
Andreas