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

Opster Team

August-23, Version: 6.8-8.1

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when you’re using a version of Elasticsearch that is 5.5.0 or later, but your configuration file is still named “elasticsearch.yaml”. This file was renamed to “elasticsearch.yml” in version 5.5.0. To resolve this issue, you can simply rename the file from “elasticsearch.yaml” to “elasticsearch.yml”. Alternatively, you can create a new “elasticsearch.yml” file and copy the contents of the old file into it. After doing this, make sure to update any references to the old file name in your scripts or applications.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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.

Log Context

Log “elasticsearch.yaml was deprecated in 5.5.0 and must be renamed to elasticsearch.yml” class name 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");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?