Log ignoring unknown index setting: with value ; archiving – How To Solve Related Issues



Log ignoring unknown index setting: with value ; archiving – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “ignoring unknown index setting: with value ; archiving” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, index, metadata, upgrade.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

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

 
    IndexMetaData archiveBrokenIndexSettings(IndexMetaData indexMetaData) {
        final Settings settings = indexMetaData.getSettings();
        final Settings upgrade = 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 (upgrade != settings) {
            return IndexMetaData.builder(indexMetaData).settings(upgrade).build();




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 low disk watermark [??%] exceeded on -views 54.99 K ,score 55

Github Issue Number 28026  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now