Skip to content

[DOCS] Correct important note for xpack.transform.enabled #52194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/reference/settings/data-frames-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@ Therefore the node cannot start or administrate {transform} or receive transport
communication requests related to {transform} APIs.
+
IMPORTANT: If you want to use {transform} features in your cluster, you must have
`xpack.transform.enabled` set to `true` on all master-eligible nodes. This is the
default behavior.
`xpack.transform.enabled` set to `true` on all master-eligible nodes and all data nodes.
This is the default behavior.

`xpack.transform.num_transform_failure_retries` (<<cluster-update-settings,Dynamic>>)::
The number of times that a {transform} retries when it experiences a
Expand Down
10 changes: 10 additions & 0 deletions docs/reference/transform/limitations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,16 @@ is returned. Use the `size` and `from` parameters to enumerate through the full
list.


[float]
[[transform-node-assignment-limitations]]
==== {transforms-cap} node assignment not configurable

{transforms-cap} persistent tasks are assigned to the data node running
fewest persistent tasks at the time of assignment. This cannot be customized.
It means that if {transforms} are being used then `xpack.transform.enabled`
must be set to `true` (which is the default) on every data node in the cluster.


[float]
[[transform-aggresponse-limitations]]
==== Aggregation responses may be incompatible with destination index mappings
Expand Down