Log Settings and are deprecated. Index settings from your old indices have been updated to record the fact that they – How To Solve Related Issues



Log 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 read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

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. 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, settings and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

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);
        }
    }

    /**






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 Sticsearch Query To Return All Reco

2 Github Issue Number 15613






Optimize Elasticsearch Performance

Try The Tool