# Elasticsearch Docker: flood stage disk watermark \[95%\] exceeded

**URL:** <https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [September 14, 2020, 7:38am UTC](https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479 "2020-09-14T07:38:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Stimmot](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@Stimmot](https://discuss.elastic.co/u/Stimmot)\
**Post date:** [September 14, 2020, 8:56am UTC](https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479/2 "2020-09-14T08:56:03Z")

</div>

I found the solution. The problem has to do with the disk usage in total as described in the answer from sastorsl here:

> <https://stackoverflow.com/questions/33369955/low-disk-watermark-exceeded-on>

I was working on a cluster the storage of which was 98% used, still there were 400GB free, but Elasticsearch only looks at the percentages, thus shutting down any write permissions of indices.

The solution is to manually set the watermarks after the nodes have started (setting them in the elasticsearch.yml didn't work for some reason):

```auto
curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_cluster/settings -d '{ "transient": { "cluster.routing.allocation.disk.threshold_enabled": false } }'
curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

```

Of course you have to put in your index names.  
After that, they will be writable again.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479)._