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

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch encounters a setting in its configuration that it doesn’t recognize. The setting is then archived for reference, but not used. This could be due to a typo, deprecated setting, or a setting from a plugin that’s not installed. To resolve this, first, identify the unknown setting mentioned in the error message. Then, check if it’s spelled correctly, still valid in your OpenSearch version, or if it’s from a missing plugin. Correct the typo, update the setting, or install the necessary plugin as needed.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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 OpenSearch concepts: settings, cluster, admin.

Log Context

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

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

    private 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 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?

Get expert answers on Elasticsearch/OpenSearch