Ignoring persistent setting ; not dynamically updateable – 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 analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when Elasticsearch is attempting to update a persistent setting that is not dynamically updateable. This error can occur when there is a conflict between the new setting value and an existing setting or when the setting is not designed to be updated dynamically. To resolve this error, you can check the setting’s documentation to see if it is dynamically updateable or not. If it is not, you will need to manually update the setting in the Elasticsearch configuration file or through the Elasticsearch API. If there is a conflict with an existing setting, you may need to modify the setting to resolve the conflict.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Ignoring persistent setting ; not dynamically updateable ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster, persistent and settings.

Log Context

Log “ignoring persistent setting [{}]; not dynamically updateable” classname is TransportClusterUpdateSettingsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             changed = true;
                        } else {
                            logger.warn("ignoring persistent setting [{}]; [{}]"; entry.getKey(); error);
                    } else {
                        logger.warn("ignoring persistent setting [{}]; not dynamically updateable"; entry.getKey());

                if (!changed) {
                    return currentState;


How useful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content