WARNING: Version 5.6 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
You do not need to configure any settings to use machine learning. It is enabled by default.
-
xpack.ml.enabled
-
Set to
true
(default) to enable machine learning on the node.
If set to
false
inelasticsearch.yml
, the machine learning APIs are disabled on the node. Therefore the node cannot open jobs, start datafeeds, or receive transport (internal) communication requests related to machine learning APIs. It also affects all Kibana instances that connect to this Elasticsearch instance; you do not need to disable machine learning in thosekibana.yml
files. For more information about disabling machine learning in specific Kibana instances, see Kibana Machine Learning Settings.If you want to use machine learning features in your cluster, you must have
xpack.ml.enabled
set totrue
on all master-eligible nodes. This is the default behavior. -
node.ml
-
Set to
true
(default) to identify the node as a machine learning node.
If set to
false
inelasticsearch.yml
, the node cannot run jobs. If set totrue
butxpack.ml.enabled
is set tofalse
, thenode.ml
setting is ignored and the node cannot run jobs. If you want to run jobs, there must be at least one machine learning node in your cluster.On dedicated coordinating nodes or dedicated master nodes, disable the
node.ml
role.