# Deleting \_recovery\_source

**URL:** https://discuss.elastic.co/t/deleting-recovery-source/327028
**Category:** Elasticsearch
**Created:** [March 6, 2023, 5:32am UTC](https://discuss.elastic.co/t/deleting-recovery-source/327028 "2023-03-06T05:32:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![kpachar](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@kpachar](https://discuss.elastic.co/u/kpachar)
#### Post date: [March 6, 2023, 5:32am UTC](https://discuss.elastic.co/t/deleting-recovery-source/327028/1 "2023-03-06T05:32:45Z")

</div>

Hi everyone,

I'm on Elasticsearch 8.6.2.

I wanted to reduce disk usage of my indices, and noticed that the `_recovery_source` takes up quite some space.

I tried setting `index.soft_deletes.enabled` to `false`, but index creation wasn't allowed by elasticsearch with that.

I then tried setting `index.soft_deletes.retention_lease.period` to `"10s"` and called the forcemerge API after writing some documents. This didn't delete the \_recovery\_source. I restarted elasticsearch and retried forcemerge, but it made no difference.

I keep retrying the forcemerge API and after some random number of attempts, it does eventually delete the \_recovery\_source.

But is there a way to reliably make elasticsearch delete \_recovery\_source?

Thank you

---

<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: [April 3, 2023, 5:33am UTC](https://discuss.elastic.co/t/deleting-recovery-source/327028/2 "2023-04-03T05:33:27Z")

</div>

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