IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Transforms settings in Elasticsearch
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Transforms settings in Elasticsearch
editYou do not need to configure any settings to use transforms. It is enabled by default.
All of these settings can be added to the elasticsearch.yml configuration file.
The dynamic settings can also be updated across a cluster with the
cluster update settings API.
Dynamic settings take precedence over settings in the elasticsearch.yml
file.
General transforms settings
edit-
node.transform -
Set to
trueto identify the node as a transform node. Ifnode.dataisfalsefor the node, the default value isfalse. Otherwise, the default value istrue.If set to
falseinelasticsearch.yml, the node cannot run transforms. If you want to run transforms, there must be at least one transform node in your cluster.On dedicated coordinating nodes or dedicated master nodes, disable the node.transform role.
-
xpack.transform.enabled -
[7.8.0]
Deprecated in 7.8.0. Basic License features should always be enabled
This deprecated setting no longer has any effect. -
xpack.transform.num_transform_failure_retries(Dynamic) -
The number of times that a transform retries when it experiences a
non-fatal error. Once the number of retries is exhausted, the transform
task will be marked as
failed. The default value is10with a valid minimum of0and maximum of100. If a transform is already running, it will have to be restarted to use the changed setting.