Settings and are deprecated. Index settings from your old indices have been updated to record the fact that they – How to solve related issues

Opster Team

Feb-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 ” Settings and are deprecated. Index settings from your old indices have been updated to record the fact that they ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, index, metadata, settings and upgrade.

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 “Settings [{}] and [{}] are deprecated. Index settings from your old indices have been updated to record the fact that they” classname is MetaDataIndexUpgradeService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         } else {
            pre20HashFunction = DjbHashFunction.class;
        }
        pre20UseType = settings.getAsBoolean(DEPRECATED_SETTING_ROUTING_USE_TYPE; null);
        if (hasCustomPre20HashFunction || pre20UseType != null) {
            logger.warn("Settings [{}] and [{}] are deprecated. Index settings from your old indices have been updated to record the fact that they "
                    + "used some custom routing logic; you can now remove these settings from your `elasticsearch.yml` file"; DEPRECATED_SETTING_ROUTING_HASH_FUNCTION; DEPRECATED_SETTING_ROUTING_USE_TYPE);
        }
    }

    /**




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content