# Disk full because of elasticsearch

**URL:** <https://community.graylog.org/t/disk-full-because-of-elasticsearch/21849>\
**Category:** Graylog Central (peer support)\
**Created:** [November 24, 2021, 2:32pm UTC](https://community.graylog.org/t/disk-full-because-of-elasticsearch/21849 "2021-11-24T14:32:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [November 26, 2021, 8:25pm UTC](https://community.graylog.org/t/disk-full-because-of-elasticsearch/21849/3 "2021-11-26T20:25:24Z")

</div>

Here is a more in depth post by @gsmith that talks about watermarks and what to do with them:

> [@Graylog stopped with timeout](https://community.graylog.org/t/graylog-stopped-with-timeout/21834/11):
>
> Hello, My apologies, I misread your post. I believe Its because of this statement in your logs. low disk watermark [85%] exceeded on Definition of low disk watermark [85%] exceeded. When disk usage on a host hits 85 percent, the Elasticsearch service prevents shard allocation and stops working. This disk usage threshold is an Elasticsearch configuration. By default, the cluster.routing.allocation.disk.watermark.low watermark is set to 85% to prevent Elasticsearch from allocating new sh…

---

_[View the full topic](https://community.graylog.org/t/disk-full-because-of-elasticsearch/21849)._