# Configure Delete indices based on size index lifecycle management Policy Elastic search **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [August 18, 2020, 5:56am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348 "2020-08-18T05:56:27Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Darshan\_Kamat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_kamat/32/44993_2.png) [@Darshan\_Kamat](https://discuss.elastic.co/u/Darshan_Kamat)\ **Post date:** [August 18, 2020, 5:56am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/1 "2020-08-18T05:56:27Z")
Version : ES 7.6.0 I have elastic search set up with filebeat for pulling up logs and rollover configured with index policy(ILM) . I have 2 phases configured : HOT and DELETE. In the delete phase for index policy there is option in kibana to delete based on number of days from rollover which i am having as 3 days. I recently faced an issue wherein load test was performed and there was sudden spike in disk usage,index policy did not delete the indices as rollover configured was 3 days . As a result there were watermark alerts after 95 % and index went into read only mode. My question is for such a scenario is there a way in index policy to delete old indices after a certain threshold of disk space is utilized instead of just configuring deletion based on number of days from last rollover of index? ---
**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:** [August 18, 2020, 6:30am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/2 "2020-08-18T06:30:56Z")
There's no disk level based trigger at this stage, check out [https://github.com/elastic/elasticsearch/issues/49392](https://github.com/elastic/elasticsearch/issues/49392) though. ---
**Author:** ![Darshan\_Kamat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_kamat/32/44993_2.png) [@Darshan\_Kamat](https://discuss.elastic.co/u/Darshan_Kamat)\ **Post date:** [August 18, 2020, 6:50am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/3 "2020-08-18T06:50:30Z")
Hi @warkolm, Thanks for your reply. I am surprised that this feature is not implemented yet as this seems to me a fairly common use case . So how to deal with such scenarios wherein there could be space crunch and I wish to delete old indices to accomodate space for new ones? ---
**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:** [August 18, 2020, 6:51am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/4 "2020-08-18T06:51:24Z")
You would currently need to monitor it yourself. ---
**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:** [August 18, 2020, 7:55am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/5 "2020-08-18T07:55:19Z")
Curator does support this as far as I know. ---
**Author:** ![Darshan\_Kamat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_kamat/32/44993_2.png) [@Darshan\_Kamat](https://discuss.elastic.co/u/Darshan_Kamat)\ **Post date:** [August 18, 2020, 8:08am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/6 "2020-08-18T08:08:40Z")
On the same lines , is there a feature where i can bind ES to use certain amount of space only on a disk like for eg 50 GB to ES on 200 GB disk ? ---
**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:** [August 18, 2020, 8:10am UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/7 "2020-08-18T08:10:19Z")
[https://www.elastic.co/guide/en/elasticsearch/reference/7.8/modules-cluster.html#disk-based-shard-allocation](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/modules-cluster.html#disk-based-shard-allocation) ---
**Author:** ![Darshan\_Kamat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darshan_kamat/32/44993_2.png) [@Darshan\_Kamat](https://discuss.elastic.co/u/Darshan_Kamat)\ **Post date:** [August 18, 2020, 12:26pm UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/8 "2020-08-18T12:26:24Z")
So value in "cluster.routing.allocation.disk.watermark.flood\_stage" will be the max value ES will use on the node . Is this understanding correct ? ---
**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:** [August 18, 2020, 8:39pm UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/9 "2020-08-18T20:39:52Z")
Yes that's right. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 15, 2020, 8:39pm UTC](https://discuss.elastic.co/t/configure-delete-indices-based-on-size-index-lifecycle-management-policy-elastic-search/245348/10 "2020-09-15T20:39:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.