Updated breaker settings parent: – How to solve related issues

Average Read Time

2 Mins

Updated breaker settings parent: – 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 ” Updated breaker settings parent: ” 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, indices and settings.

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 “Updated breaker settings parent: {}” classname is HierarchyCircuitBreakerService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             ByteSizeValue newParentMax = settings.getAsMemory(TOTAL_CIRCUIT_BREAKER_LIMIT_SETTING; null);
            if (newParentMax != null && (newParentMax.bytes() != oldParentMax)) {
                BreakerSettings newParentSettings = new BreakerSettings(CircuitBreaker.PARENT; newParentMax.bytes(); 1.0; CircuitBreaker.Type.PARENT);
                validateSettings(new BreakerSettings[]{newParentSettings});
                HierarchyCircuitBreakerService.this.parentSettings = newParentSettings;
                logger.info("Updated breaker settings parent: {}"; newParentSettings);



Run the Check-Up to get a customized report like this:

Analyze your cluster