Ignoring existing unknown 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 run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

                         .build();
                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; final IllegalArgumentException ex; final Logger logger) {
        logger.warn(




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content