Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
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)) {
Find & fix Elasticsearch problems
