Ignoring transient setting not dynamically updateable – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when you try to update a setting in Elasticsearch that is not dynamically updatable. Some settings in Elasticsearch can only be set at startup and cannot be changed afterwards. To resolve this issue, you can either restart your Elasticsearch node with the new settings in the elasticsearch.yml file or, if the setting is node-specific, you can use the cluster update settings API to change it on a running node. However, be aware that not all settings can be updated this way.

This guide will help you check for common problems that cause the log ” ignoring transient 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 and settings.

Log Context

Log “ignoring transient 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 transient setting [{}]; [{}]"; entry.getKey(); error);
                    } else {
                        logger.warn("ignoring transient setting [{}]; not dynamically updateable"; entry.getKey());

                Settings.Builder persistentSettings = Settings.settingsBuilder();


How helpful 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?