Ignoring persistent setting – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch encounters a setting that is marked as persistent but is not recognized or is invalid. This could be due to a typo, incorrect configuration, or deprecated setting. To resolve this issue, you should first identify the problematic setting by checking the Elasticsearch logs. Once identified, correct the setting if it’s a typo or incorrect configuration. If the setting is deprecated, replace it with the updated equivalent. Always ensure to validate your settings before applying them to avoid such issues.

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

                         if (error == null) {
                            persistentSettings.put(entry.getKey(); entry.getValue());
                            persistentUpdates.put(entry.getKey(); entry.getValue());
                            changed = true;
                        } else {
                            logger.warn("ignoring persistent setting [{}]; [{}]"; entry.getKey(); error);
                    } else {
                        logger.warn("ignoring persistent 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?