Ignoring existing unknown setting with value archiving – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters a setting in its configuration that it doesn’t recognize. In this case, the setting is “archiving”. This could be due to a typo, deprecated setting, or a setting that’s not applicable to the current version of Elasticsearch. To resolve this issue, you can either remove the unknown setting from the configuration file or replace it with a valid one. If it’s a deprecated setting, you should find the updated equivalent and use that instead. Always ensure that your settings are compatible with your Elasticsearch version.

This guide will help you check for common problems that cause the log ” ignoring existing unknown {} setting: [{}] with value [{}]; archiving ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, cluster, settings.

Log Context

Log “ignoring existing unknown {} setting: [{}] with value [{}]; archiving” classname is SettingsUpdater.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            settingsWithUnknownOrInvalidArchived.filter(k -> k.startsWith(ARCHIVED_SETTINGS_PREFIX))

    private static void logUnknownSetting(final String settingType; final Map.Entry e; final Logger logger) {
        logger.warn("ignoring existing unknown {} setting: [{}] with value [{}]; archiving"; settingType; e.getKey(); e.getValue());

    private static void logInvalidSetting(
        final String settingType;
        final Map.Entry e;


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?