Ignoring gc threshold for missing warn info debug values – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when the Garbage Collection (GC) thresholds for warn, info, or debug levels are not properly set in Elasticsearch’s configuration. Elasticsearch uses these thresholds to trigger GC logs at different levels. If these values are missing, it will ignore the GC threshold. To resolve this issue, you can check your Elasticsearch configuration file (elasticsearch.yml) and ensure that the GC thresholds for warn, info, and debug are correctly set. Alternatively, you can set these values using the cluster update settings API if you want to change them dynamically.

This guide will help you check for common problems that cause the log ” ignoring gc_threshold for [{}]; missing warn/info/debug values ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: monitor.

Log Context

Log “ignoring gc_threshold for [{}]; missing warn/info/debug values” classname is JvmMonitorService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             String name = entry.getKey();
            TimeValue warn = entry.getValue().getAsTime("warn"; null);
            TimeValue info = entry.getValue().getAsTime("info"; null);
            TimeValue debug = entry.getValue().getAsTime("debug"; null);
            if (warn == null || info == null || debug == null) {
                logger.warn("ignoring gc_threshold for [{}]; missing warn/info/debug values"; name);
            } else {
                gcThresholds.put(name; new GcThreshold(name; warn.millis(); info.millis(); debug.millis()));
        if (!gcThresholds.containsKey(GcNames.YOUNG)) {