New used memory from field would be larger than configured breaker: ; breaking – How to solve related issues

Average Read Time

2 Mins

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 run 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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content