honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Add ML cross cluster search limitation (elastic/x-pack-elasticsearch#1314) 

* [DOCS] Add ML cross cluster search limitation

* [DOCS] Clarify node.ml setting

Original commit: elastic/x-pack-elasticsearch@19a0c5d822
This commit is contained in:
Lisa Cawley 2017-05-16 08:19:25 -07:00 committed by GitHub
parent f8531004a8
commit 446a08b391
2 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/en/ml/limitations.asciidoc
View File

@ -8,10 +8,9 @@ The following limitations and known problems apply to the {version} release of
=== Pop-ups must be enabled in browsers
//See x-pack-elasticsearch/#844
The {xpackml} features in Kibana use pop-ups. You must configure your
The {xpackml} features in {kib} use pop-ups. You must configure your
web browser so that it does not block pop-up windows or create an
exception for your Kibana URL.
exception for your {kib} URL.
[float]
=== Jobs must be re-created at GA
@ -23,6 +22,14 @@ re-create your jobs. If you have data sets and job configurations that
you work with extensively in the beta, make note of all the details so
that you can re-create them successfully.
[float]
=== {xpackml} features do not support cross cluster search
You cannot use cross cluster search in either the {ml} APIs or the {ml}
features in {kib}.
For more information about cross cluster search,
see {ref}/modules-cross-cluster-search.html[Cross Cluster Search].
[float]
=== Anomaly Explorer omissions and limitations

13
docs/en/settings/ml-settings.asciidoc
View File

@ -13,17 +13,18 @@ If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled.
You also cannot open jobs or start {dfeeds}.
If set to `false` in `kibana.yml`, the {ml} icon is not visible in {kib}. +
+
TIP: If you want to use {ml} features in your cluster, you must enable {ml} on
all master-eligible nodes. This is the default behavior.
IMPORTANT: If you want to use {ml} features in your cluster, you must enable
{ml} 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` in `elasticsearch.yml`, the node cannot run jobs.
If you want to run jobs, there must be at least one machine learning node
in your cluster. +
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. +
+
TIP: On dedicated coordinating nodes or dedicated master nodes, disable
IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable
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