How To Solve Issues Related to Log – New used memory for data ofwould be larger than configured breaker:; breaking

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Dec-19

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “New used memory for data ofwould be larger than configured breaker:; breaking” it’s important to understand common problems related to Elasticsearch concepts: memory. See detailed explanations below complete with common problems, examples and useful tips.

Memory in Elasticsearch

What is it

Memory is one of the most critical resources to monitor in Elasticsearch. Elasticsearch runs on JVM and uses heap memory areas for query cache, request cache, accessing lucene segments and storing fielddata for aggregations and sorting.

Commos problems and important points
  • The most common error that arises in Elasticsearch is OutOfMemory error. This error comes when the node is not able to cope up with the required heap size space. To avoid this, you need to closely monitor the heap utilization and garbage collector performance.
  • As per the most up-to-date best practices you should not allocate more than 50 percent of total RAM to JVM heap size. Starting from Elasticsearch version 5.x onward this can be set using -Xms and -Xmx parameters inside jvm.options configuration file. The defaults are set to 1 GB for both minimum and maximum heap size.
  • The heap size should not set more than 31 GB in any case to avoid the poor garbage collection.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 FIELDDATA Data is too large 17.22 K 13

2New Used Memory 6 4Gb For Data Of R  

Es Memory Breaker Configuration


Log Context

Log ”New used memory[{}] for data ofwould be larger than configured breaker:[{}]; breaking” classname is ChildMemoryCircuitBreaker.java
We have extracted the following from Elasticsearch source code to get 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 {} [{}] for data of [{}] would be larger than configured breaker: {} [{}]; breaking";
                        this.name;
                        newUsedWithOverhead; new ByteSizeValue(newUsedWithOverhead); label;
                        memoryBytesLimit; new ByteSizeValue(memoryBytesLimit));
                circuitBreak(label; newUsedWithOverhead);
            }



About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster