Low disk watermark no longer exceeded on – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when the disk space on a node in an OpenSearch cluster falls below the “low disk watermark” threshold, but then recovers. OpenSearch uses watermarks to protect against running out of disk space. When the low watermark is exceeded, OpenSearch will stop allocating new shards to the node. To resolve this issue, you can either increase your disk space, delete unnecessary data, or adjust the watermark thresholds in the OpenSearch settings. However, be careful with the last option as it could lead to a risk of running out of disk space.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” low disk watermark [{}] no longer exceeded on {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: allocation, routing, cluster.

Log Context

Log “low disk watermark [{}] no longer exceeded on {}” classname is DiskThresholdMonitor.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                        reroute = true;
                        explanation = "one or more nodes has gone under the high or low watermark";

                        logger.info("low disk watermark [{}] no longer exceeded on {}";
                            diskThresholdSettings.describeLowThreshold(); usage);

                    } else {
                        logger.debug("{} has gone below a disk threshold; but an automatic reroute has occurred " +
                                "in the last [{}]; skipping reroute";


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch