Ignoring gc-threshold for ; missing warn/info/debug values – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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)) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content