Log Last_gc duration . collections . total . reclaimed . leaving – How To Solve Related Issues



Log Last_gc duration . collections . total . reclaimed . leaving – 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Last_gc duration . collections . total . reclaimed . leaving” 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”[last_gc][{}][{}][{}] duration [{}]; collections [{}]; total [{}]/[{}]; reclaimed [{}]; leaving [{}][{}]/[{}]” classname is JvmMonitorService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     // Ignore any duration > 1hr; getLastGcInfo occasionally returns total crap
                    if (lastGc.duration().hoursFrac() > 1) {
                        continue;
                    }
                    if (lastGc.duration().millis() > gcThreshold.warnThreshold) {
                        logger.warn("[last_gc][{}][{}][{}] duration [{}]; collections [{}]; total [{}]/[{}]; reclaimed [{}]; leaving [{}][{}]/[{}]";
                                gc.name(); seq; gc.getCollectionCount(); lastGc.duration(); collections; TimeValue.timeValueMillis(collectionTime); gc.collectionTime(); lastGc.reclaimed(); lastGc.afterUsed(); lastGc.max());
                    } else if (lastGc.duration().millis() > gcThreshold.infoThreshold) {
                        logger.info("[last_gc][{}][{}][{}] duration [{}]; collections [{}]; total [{}]/[{}]; reclaimed [{}]; leaving [{}]/[{}]";
                                gc.name(); seq; gc.getCollectionCount(); lastGc.duration(); collections; TimeValue.timeValueMillis(collectionTime); gc.collectionTime(); lastGc.reclaimed(); lastGc.afterUsed(); lastGc.max());
                    } else if (lastGc.duration().millis() > gcThreshold.debugThreshold && logger.isDebugEnabled()) {




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

 

   

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now