Log gc duration ; collections /; total /; memory>/; all-pools – How To Solve Related Issues



Log gc duration ; collections /; total /; memory>/; all-pools – 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 “gc duration ; collections /; total /; memory>/; all-pools” 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: memory, 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”[gc][{}][{}][{}] duration [{}]; collections [{}]/[{}]; total [{}]/[{}]; memory [{}]->[{}]/[{}]; all_pools {}” classname is JvmMonitorService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
                if (avgCollectionTime > gcThreshold.warnThreshold) {
                    logger.warn("[gc][{}][{}][{}] duration [{}]; collections [{}]/[{}]; total [{}]/[{}]; memory [{}]->[{}]/[{}]; all_pools {}";
                            gc.getName(); seq; gc.getCollectionCount(); TimeValue.timeValueMillis(collectionTime); collections; TimeValue.timeValueMillis(currentJvmStats.getTimestamp() - lastJvmStats.getTimestamp()); TimeValue.timeValueMillis(collectionTime); gc.getCollectionTime(); lastJvmStats.getMem().getHeapUsed(); currentJvmStats.getMem().getHeapUsed(); JvmInfo.jvmInfo().getMem().getHeapMax(); buildPools(lastJvmStats; currentJvmStats));
                } else if (avgCollectionTime > gcThreshold.infoThreshold) {
                    logger.info("[gc][{}][{}][{}] duration [{}]; collections [{}]/[{}]; total [{}]/[{}]; memory [{}]->[{}]/[{}]; all_pools {}";
                            gc.getName(); seq; gc.getCollectionCount(); TimeValue.timeValueMillis(collectionTime); collections; TimeValue.timeValueMillis(currentJvmStats.getTimestamp() - lastJvmStats.getTimestamp()); TimeValue.timeValueMillis(collectionTime); gc.getCollectionTime(); lastJvmStats.getMem().getHeapUsed(); currentJvmStats.getMem().getHeapUsed(); JvmInfo.jvmInfo().getMem().getHeapMax(); buildPools(lastJvmStats; currentJvmStats));
                } else if (avgCollectionTime > gcThreshold.debugThreshold && logger.isDebugEnabled()) {
                    logger.debug("[gc][{}][{}][{}] duration [{}]; collections [{}]/[{}]; total [{}]/[{}]; memory [{}]->[{}]/[{}]; all_pools {}";
                            gc.getName(); seq; gc.getCollectionCount(); TimeValue.timeValueMillis(collectionTime); collections; TimeValue.timeValueMillis(currentJvmStats.getTimestamp() - lastJvmStats.getTimestamp()); TimeValue.timeValueMillis(collectionTime); gc.getCollectionTime(); lastJvmStats.getMem().getHeapUsed(); currentJvmStats.getMem().getHeapUsed(); JvmInfo.jvmInfo().getMem().getHeapMax(); buildPools(lastJvmStats; currentJvmStats));
                }




 

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 :

1 Garbage Collection Log Messages Mon  

Gc Takes A Lot Of Time  

 

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