# How to free disk space for enterprise search?

**URL:** <https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [February 17, 2022, 10:10am UTC](https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471 "2022-02-17T10:10:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nagib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nagib/32/100670_2.png) [@Nagib](https://discuss.elastic.co/u/Nagib)\
**Post date:** [February 17, 2022, 10:10am UTC](https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471/1 "2022-02-17T10:10:40Z")

</div>

Hi, I'm currently facing an issue and I don't really know how to fix it. Recently, my script for updating my engines is returning errors while I'm trying to delete/update documents on my engines. I saw into logs the current errors messages that keeps repeating itself everytime a new action is ran :

`Exception: Exception while performing Work::Cron::RefreshFritoPieContentSources.perform()!: Swiftype::ES::ReadOnlyModeWriteError: index [.ent-search-db-lock] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];`

It looks like App search is putting my indexes in readonly due to a small amount of disk space.

I've seen online that there are some command lines :  
`curl -X PUT -H "Content-Type: application/json" http://127.0.0.1:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}`

but these are for Elasticsearch, so I don't know if I can use it here as App-search uses Elasticsearch too...

---

<div class="post-metadata">

**Author:** ![Vadim\_Yakhin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vadim_yakhin/32/56723_2.png) [@Vadim\_Yakhin](https://discuss.elastic.co/u/Vadim_Yakhin)\
**Post date:** [February 17, 2022, 6:34pm UTC](https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471/2 "2022-02-17T18:34:45Z")

</div>

Hi @Nagib! 👋

I think Elasticsearch is blocking writes because of low disk space and App Search interpreting it as read-only mode. I would try to solve this problem on the Elasticsearch side.

Also found this post, maybe it'll help: [Elasticsearch Docker: flood stage disk watermark [95%] exceeded](https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479)

---

<div class="post-metadata">

**Author:** ![Nagib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nagib/32/100670_2.png) [@Nagib](https://discuss.elastic.co/u/Nagib)\
**Post date:** [February 18, 2022, 9:03am UTC](https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471/3 "2022-02-18T09:03:40Z")

</div>

Hi @Vadim_Yakhin , I ran this command :

`curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'`  
and it seems to have solved the problem, thank you for the help !

---

<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:** [March 18, 2022, 9:04am UTC](https://discuss.elastic.co/t/how-to-free-disk-space-for-enterprise-search/297471/4 "2022-03-18T09:04:05Z")

</div>

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