Ignoring invalid index 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 an invalid index setting is detected by Elasticsearch. The setting ‘archiving’ is not recognized by Elasticsearch, hence it is ignored. To resolve this issue, you should review your index settings and remove or correct the invalid setting. Ensure that all settings are spelled correctly and are supported by your version of Elasticsearch. If ‘archiving’ is a custom setting, make sure it is implemented correctly. Also, always validate your settings before applying them to avoid such errors.

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

Log Context

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

        final Settings settings = indexMetadata.getSettings();
        final Settings newSettings = indexScopedSettings.archiveUnknownOrInvalidSettings(
            settings;
            e -> logger.warn("{} ignoring unknown index setting: [{}] with value [{}]; archiving";
                indexMetadata.getIndex(); e.getKey(); e.getValue());
            (e; ex) -> logger.warn(() -> new ParameterizedMessage("{} ignoring invalid index setting: [{}] with value [{}]; archiving";
                indexMetadata.getIndex(); e.getKey(); e.getValue()); ex));
        if (newSettings != settings) {
            return IndexMetadata.builder(indexMetadata).settings(newSettings).build();
        } else {
            return indexMetadata;

 

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?