Ignoring transient setting – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when a temporary or “transient” setting in Elasticsearch is being ignored. This usually happens when the setting is not recognized or is incompatible with the current Elasticsearch configuration. To resolve this issue, you can check the Elasticsearch documentation to ensure the setting is valid. If it is, ensure it’s compatible with your current version of Elasticsearch. If the setting is deprecated, you should replace it with the updated setting. Lastly, check your Elasticsearch logs for more detailed error messages that can help identify the problem.

This guide will help you check for common problems that cause the log ” ignoring transient setting [{}]; [{}] ” 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 [{}]; [{}]” classname is TransportClusterUpdateSettingsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         if (error == null) {
                            transientSettings.put(entry.getKey(); entry.getValue());
                            transientUpdates.put(entry.getKey(); entry.getValue());
                            changed = true;
                        } else {
                            logger.warn("ignoring transient setting [{}]; [{}]"; entry.getKey(); error);
                    } else {
                        logger.warn("ignoring transient setting [{}]; not dynamically updateable"; entry.getKey());


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?