How To Solve Issues Related to Log – is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed.

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Feb-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed.” it’s important to know common problems related to Elasticsearch concepts: bootstrap. See below-detailed explanations complete with common problems, examples and useful tips.

Search in Elasticsearch

What it is

Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET request to _search endpoint. The search query can either be provided in query string or through  a request body.

Examples

When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.

GET my_documents/_search

A JSON object is returned in response to a search query. A 200 response code will mean the request completed successfully.

{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}
Notes
  • Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
  • There are two phases of search: the query phase and the fetch phase.
  • In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list. 
  • In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
  • A coordinating node needs enough memory and CPU in order to handle the fetch phase.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1. Can’t start elasticsearch on Ubuntu 10.4 – es.default.config is no longer supported – Stats : ♥ 0.96 K  Ι √ 2

2. Github Issue Number 16306      


Log Context

Log ”is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed.” classname is Bootstrap.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

     }

    private static void checkUnsetAndMaybeExit(String confFileSetting; String settingName) {
        if (confFileSetting != null && confFileSetting.isEmpty() == false) {
            ESLogger logger = Loggers.getLogger(Bootstrap.class);
            logger.info("{} is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed."; settingName);
            exit(1);
        }
    }

    
SuppressForbidden(reason = "Allowed to exit explicitly in bootstrap phase")





About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?