Log New used memory from field would be larger than configured breaker: ; breaking – How To Solve Related Issues


Log New used memory from field would be larger than configured breaker: ; breaking – 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 ” New used memory from field would be larger than configured breaker: ; breaking ” 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: breaker, circuit and memory.

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 “New used memory {} [{}] from field [{}] would be larger than configured breaker: {} [{}]; breaking” classname is MemoryCircuitBreaker.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         new ByteSizeValue(bytes); label; new ByteSizeValue(newUsed);
                        memoryBytesLimit; new ByteSizeValue(memoryBytesLimit);
                        newUsedWithOverhead; new ByteSizeValue(newUsedWithOverhead));
            }
            if (memoryBytesLimit > 0 && newUsedWithOverhead > memoryBytesLimit) {
                logger.warn("New used memory {} [{}] from field [{}] would be larger than configured breaker: {} [{}]; breaking";
                        newUsedWithOverhead; new ByteSizeValue(newUsedWithOverhead); label;
                        memoryBytesLimit; new ByteSizeValue(memoryBytesLimit));
                circuitBreak(label; newUsedWithOverhead);
            }
            // Attempt to set the new used value; but make sure it hasn't changed




 

Optimize Elasticsearch Performance

Try The Tool