Elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml – How to solve this Elasticsearch error

Average Read Time

2 Mins

Elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

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 “elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml”classname  is InternalSettingsPreparer.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Settings.Builder output = Settings.builder();
 initializeSettings(output; input; properties);
 Environment environment = new Environment(output.build(); configPath); 
 if (Files.exists(environment.configFile().resolve("elasticsearch.yaml"))) {
 throw new SettingsException("elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml");
 } 
 if (Files.exists(environment.configFile().resolve("elasticsearch.json"))) {
 throw new SettingsException("elasticsearch.json was deprecated in 5.5.0 and must be converted to elasticsearch.yml");
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content