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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “New used memory from field would be larger than configured breaker: ; breaking” it’s important to understand a few problems related to Elasticsearch concepts breaker, circuit, memory. See bellow important tips and explanations on these concepts

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




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 How can I prevent Elasticsearch from using so much memory? 1.07 K 1

Es Breaker Memory Limit  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now