# Disk space and read\_only\_allow\_delete

**URL:** <https://discuss.elastic.co/t/disk-space-and-read-only-allow-delete/209739>\
**Category:** Elasticsearch\
**Created:** [November 27, 2019, 5:42pm UTC](https://discuss.elastic.co/t/disk-space-and-read-only-allow-delete/209739 "2019-11-27T17:42:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dale.busse](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@dale.busse](https://discuss.elastic.co/u/dale.busse)\
**Post date:** [November 27, 2019, 5:42pm UTC](https://discuss.elastic.co/t/disk-space-and-read-only-allow-delete/209739/1 "2019-11-27T17:42:00Z")

</div>

Question about the setting read\_only\_allow\_delete. We ran out of disk space, created more space and set that setting to false so indexes could be written to again and all is working fine. So now that we are operational, is there anything that need to be done to make sure that the disk safe guard is put back? Or if we reach 95% watermark again, will re-trigger? Do I need to add a setting back?

---

<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:** [December 25, 2019, 5:42pm UTC](https://discuss.elastic.co/t/disk-space-and-read-only-allow-delete/209739/2 "2019-12-25T17:42:02Z")

</div>

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