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

Opster Team

Aug-23, Version: 6.8-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch encounters a setting in its configuration that it doesn’t recognize, in this case, “archiving”. This could be due to a typo, deprecated setting, or a setting that doesn’t exist. To resolve this issue, you can check the Elasticsearch documentation to verify the correct settings. If the setting is deprecated, find the updated equivalent. If it’s a typo, correct it. If the setting doesn’t exist, remove it from the configuration. After making changes, restart Elasticsearch to apply them.

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 unknown {} setting: [{}] with value [{}]; archiving ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

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

        return ClusterState.builder(clusterState).metadata(metadataBuilder).build();

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

    private static void logInvalidSetting(final String settingType; final Map.Entry e; final IllegalArgumentException ex) {
            () -> format("ignoring invalid %s setting: [%s] with value [%s]; archiving"; settingType; e.getKey(); e.getValue());


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?