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

Opster Team

Aug-23, Version: 6.8-7.15

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 or is invalid. In this case, the setting with value “archiving” is not recognized. To resolve this issue, you can either remove the invalid setting from the configuration file or replace it with a valid one. Ensure that all settings are correctly spelled and are supported by your version of Elasticsearch. Restart Elasticsearch after making these changes for them to take effect.

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 invalid {} 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 invalid {} setting: [{}] with value [{}]; archiving” classname is ClusterStateUpdaters.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        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) {
        logger.warn(() -> new ParameterizedMessage("ignoring invalid {} setting: [{}] with value [{}]; archiving";
                settingType; e.getKey(); e.getValue()); ex);

    static ClusterState recoverClusterBlocks(final ClusterState state) {
        final ClusterBlocks.Builder blocks = ClusterBlocks.builder().blocks(state.blocks());


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?