2017-06-19 21:01:52 -04:00
|
|
|
[role="xpack"]
|
2017-04-17 14:53:31 -04:00
|
|
|
[[ml-settings]]
|
2017-06-19 21:01:52 -04:00
|
|
|
=== Machine Learning Settings
|
2017-04-27 13:51:48 -04:00
|
|
|
You do not need to configure any settings to use {ml}. It is enabled by default.
|
2017-04-17 14:53:31 -04:00
|
|
|
|
|
|
|
[float]
|
|
|
|
[[general-ml-settings]]
|
2017-06-19 21:01:52 -04:00
|
|
|
==== General Machine Learning Settings
|
2017-04-17 14:53:31 -04:00
|
|
|
|
|
|
|
`xpack.ml.enabled`::
|
|
|
|
Set to `true` (default) to enable {ml}. +
|
|
|
|
+
|
|
|
|
If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled.
|
2017-06-05 16:02:12 -04:00
|
|
|
You also cannot open jobs, start {dfeeds}, or receive transport (internal)
|
2017-06-19 21:01:52 -04:00
|
|
|
communication requests related to {ml} APIs. +
|
2017-04-17 14:53:31 -04:00
|
|
|
+
|
2017-06-05 16:02:12 -04:00
|
|
|
IMPORTANT: If you want to use {ml} features in your cluster, you must have
|
|
|
|
`xpack.ml.enabled` set to `true` on all master-eligible nodes. This is the
|
|
|
|
default behavior.
|
2017-04-17 14:53:31 -04:00
|
|
|
|
|
|
|
`node.ml`::
|
|
|
|
Set to `true` (default) to identify the node as a _machine learning node_. +
|
|
|
|
+
|
2017-05-16 11:19:25 -04:00
|
|
|
If set to `false` in `elasticsearch.yml`, the node cannot run jobs. If set to
|
|
|
|
`true` but `xpack.ml.enabled` is set to `false`, the `node.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. +
|
2017-04-17 14:53:31 -04:00
|
|
|
+
|
2017-05-16 11:19:25 -04:00
|
|
|
IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable
|
2017-04-17 14:53:31 -04:00
|
|
|
the `node.ml` role.
|