From bc9170387ac93c9d5b6c30f94bafca90b5fd99fb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Mon, 17 Aug 2020 16:15:53 +0200 Subject: [PATCH] [DOCS] Adds clarification to node roles (#61206) (#61211) --- docs/reference/modules/node.asciidoc | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/reference/modules/node.asciidoc b/docs/reference/modules/node.asciidoc index 4a751030780..a02c6248702 100644 --- a/docs/reference/modules/node.asciidoc +++ b/docs/reference/modules/node.asciidoc @@ -1,8 +1,8 @@ [[modules-node]] === Node -Any time that you start an instance of Elasticsearch, you are starting a _node_. -A collection of connected nodes is called a <>. If you +Any time that you start an instance of {es}, you are starting a _node_. A +collection of connected nodes is called a <>. If you are running a single node of {es}, then you have a cluster of one node. Every node in the cluster can handle <> and @@ -22,6 +22,15 @@ TIP: As the cluster grows and in particular if you have large {ml} jobs or {ctransforms}, consider separating dedicated master-eligible nodes from dedicated data nodes, {ml} nodes, and {transform} nodes. +[[node-roles]] +==== Nore roles + +You can define the roles of a node by setting `node.roles`. If you don't +configure this setting, then the node has the following roles by default: +`master`, `data`, `ingest`, `transform`, `ml`. + +If you set node.roles, the node is assigned only the roles you specify. + <>:: A node that has the `master` role (default), which makes it eligible to be