[DOCS] Clarify ML node settings re transport requests (elastic/x-pack-elasticsearch#1641)

* [DOCS] Clarify ML node settings re transport requests

* [DOCS] Clarify xpack.ml.enabled based on feedback

Original commit: elastic/x-pack-elasticsearch@3102d1e3f3
This commit is contained in:
Lisa Cawley 2017-06-05 13:02:12 -07:00 committed by GitHub
parent 5f76bbd58d
commit 17d75acb7a
1 changed files with 5 additions and 5 deletions

View File

@ -10,11 +10,13 @@ You do not need to configure any settings to use {ml}. It is enabled by default.
Set to `true` (default) to enable {ml}. + Set to `true` (default) to enable {ml}. +
+ +
If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled. If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled.
You also cannot open jobs or start {dfeeds}. You also cannot open jobs, start {dfeeds}, or receive transport (internal)
communication requests related to {ml} APIs.
If set to `false` in `kibana.yml`, the {ml} icon is not visible in {kib}. + If set to `false` in `kibana.yml`, the {ml} icon is not visible in {kib}. +
+ +
IMPORTANT: If you want to use {ml} features in your cluster, you must enable IMPORTANT: If you want to use {ml} features in your cluster, you must have
{ml} on all master-eligible nodes. This is the default behavior. `xpack.ml.enabled` set to `true` on all master-eligible nodes. This is the
default behavior.
`node.ml`:: `node.ml`::
Set to `true` (default) to identify the node as a _machine learning node_. + Set to `true` (default) to identify the node as a _machine learning node_. +
@ -26,5 +28,3 @@ least one machine learning node in your cluster. +
+ +
IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable
the `node.ml` role. the `node.ml` role.
//Eventually this node information should be added to https://www.elastic.co/guide/en/elasticsearch/reference/5.3/modules-node.html