[DOCS] Replaces transform.node with node.roles: [ transform ] in transforms settings. (#61267) (#61271)

This commit is contained in:
István Zoltán Szabó 2020-08-18 18:00:06 +02:00 committed by GitHub
parent 7596bb7454
commit 78d77ebed7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 16 deletions

View File

@ -21,27 +21,24 @@ file.
[[general-transform-settings]] [[general-transform-settings]]
==== General {transforms} settings ==== General {transforms} settings
`node.transform`:: `node.roles: [ transform ]`::
deprecated:[7.9.0,"Use <<modules-node,node.roles>> instead."] Set to `node.roles` to contain `transform` to identify the node as a _transform
Set to `true` to identify the node as a _transform node_. If `node.data` node_. If you use the default settings for a node, it does not have the
is `false` for the node, the default value is `false`. Otherwise, the default `transform` role.
value is `true`.
+ +
If set to `false` in `elasticsearch.yml`, the node cannot run transforms. If If a node doesn't have this role, the node cannot run transforms. If you want to
you want to run transforms, there must be at least one transform node in your run transforms, there must be at least one transform node in your cluster.
cluster. +
+ +
IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable If you use the `node.roles` setting, then all required roles must be explicitly
the node.transform role. set. Consult <<modules-node>> to learn more.
`xpack.transform.enabled`:: `xpack.transform.enabled`::
deprecated:[7.8.0,Basic License features should always be enabled] + deprecated:[7.8.0,Basic License features should always be enabled] +
This deprecated setting no longer has any effect. This deprecated setting no longer has any effect.
`xpack.transform.num_transform_failure_retries` (<<cluster-update-settings,Dynamic>>):: `xpack.transform.num_transform_failure_retries` (<<cluster-update-settings,Dynamic>>)::
The number of times that a {transform} retries when it experiences a The number of times that a {transform} retries when it experiences a non-fatal
non-fatal error. Once the number of retries is exhausted, the {transform} error. Once the number of retries is exhausted, the {transform} task is marked
task will be marked as `failed`. The default value is `10` with a valid minimum of `0` as `failed`. The default value is `10` with a valid minimum of `0` and maximum
and maximum of `100`. of `100`. If a {transform} is already running, it has to be restarted to use the
If a {transform} is already running, it will have to be restarted changed setting.
to use the changed setting.