Briefly, this error occurs when an attempt is made to access the job manager while the Machine Learning (ML) feature is disabled in Elasticsearch. To resolve this issue, you can enable the ML feature by setting the ‘xpack.ml.enabled’ parameter to true in the Elasticsearch configuration file (elasticsearch.yml). Alternatively, you can avoid accessing ML features if you don’t intend to use them. If you’re using a cloud service, ensure your subscription includes ML.
This guide will help you check for common problems that cause the log ” Tried to get job manager although Machine Learning is disabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Tried to get job manager although Machine Learning is disabled” class name is JobManagerHolder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
* @return job manager instance
* @throws ElasticsearchException if holder has been created with the empty constructor
*/
public JobManager getJobManager() {
if (instance == null) {
throw new ElasticsearchException("Tried to get job manager although Machine Learning is disabled");
}
return instance;
}
}
