Log Ignoring gc-threshold for ; missing warn/info/debug values – How To Solve Related Issues


Log 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 try running the 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: monitor.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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




 





Optimize Elasticsearch Performance

Try The Tool