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

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when the disk space on a node falls below the “low disk watermark” threshold, which is a set limit in Elasticsearch to prevent the node from running out of disk space. The error message indicates that the disk space has now increased above this threshold. To avoid this error, you can increase the disk space, reduce the index size by deleting unnecessary data, or adjust the “low disk watermark” setting to a lower percentage. Also, consider setting up monitoring and alerts to be notified when disk space is running low.

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 Elasticsearch concepts: cluster, routing, allocation.

Log Context

Log “low disk watermark [{}] no longer exceeded on {}” classname is DiskThresholdMonitor.java.
We extracted the following from Elasticsearch 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?