# Is it safe to delete logs-deprecation indices, where can we disable creation of these indices?

**URL:** <https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714>\
**Category:** Elasticsearch\
**Created:** [August 25, 2023, 6:46pm UTC](https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714 "2023-08-25T18:46:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vadym](https://avatars.discourse-cdn.com/v4/letter/v/8baadc/32.png) [@Vadym](https://discuss.elastic.co/u/Vadym)\
**Post date:** [August 25, 2023, 6:46pm UTC](https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714/1 "2023-08-25T18:46:43Z")

</div>

We have some system indices generated by ES, can we turn off generation of these indices and is it safe to delete them?

health status index  
green open .ds-ilm-history-5-2023.06.02-000012  
green open .ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017  
green open .ds-.logs-deprecation.elasticsearch-default-2023.07.02-000015  
green open .ds-ilm-history-5-2023.07.02-000014  
green open .ds-ilm-history-5-2023.08.01-000016

---

<div class="post-metadata">

**Author:** ![Vadym](https://avatars.discourse-cdn.com/v4/letter/v/8baadc/32.png) [@Vadym](https://discuss.elastic.co/u/Vadym)\
**Post date:** [August 25, 2023, 9:36pm UTC](https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714/2 "2023-08-25T21:36:23Z")

</div>

It seems these indices can't be deleted even when Ilm is stopped:

```auto
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"index [.ds-ilm-history-5-2023.08.01-000016] is the write index for data stream [ilm-history-5] and cannot be deleted"}],"type":"illegal_argument_exception","reason":"index [.ds-ilm-history-5-2023.08.01-000016] is the write index for data stream [ilm-history-5] and cannot be deleted"},"status":400}%

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"index [.ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017] is the write index for data stream [.logs-deprecation.elasticsearch-default] and cannot be deleted"}],"type":"illegal_argument_exception","reason":"index [.ds-.logs-deprecation.elasticsearch-default-2023.08.01-000017] is the write index for data stream [.logs-deprecation.elasticsearch-default] and cannot be deleted"},"status":400}%

```

---

<div class="post-metadata">

**Author:** ![Vadym](https://avatars.discourse-cdn.com/v4/letter/v/8baadc/32.png) [@Vadym](https://discuss.elastic.co/u/Vadym)\
**Post date:** [August 28, 2023, 9:34pm UTC](https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714/3 "2023-08-28T21:34:44Z")

</div>

Maybe someone can point me to the right documentation. Currently I can't delete last index of a data stream whether ILM is turned on or off.

"You cannot delete the current write index of a data stream. To delete the index, you must roll over the data stream so a new write index is created. You can then use the delete index API to delete the previous write index."

Also I can't increase the replication factor on these indices, cluster acknowledges the change but replication factor stays at 1, creating fake "RED" status conditions.

---

<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:** [September 25, 2023, 9:35pm UTC](https://discuss.elastic.co/t/is-it-safe-to-delete-logs-deprecation-indices-where-can-we-disable-creation-of-these-indices/341714/4 "2023-09-25T21:35:06Z")

</div>

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