From dd19bc8d63ffbb1626e7611ef0cf5cccc8244857 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Tue, 4 Mar 2025 08:54:47 -0500 Subject: [PATCH 1/2] Update node-settings.md Port change https://github.com/elastic/elasticsearch/pull/123939 forward to new docs system --- .../elasticsearch/configuration-reference/node-settings.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/reference/elasticsearch/configuration-reference/node-settings.md b/docs/reference/elasticsearch/configuration-reference/node-settings.md index 3a9634a37fc6b..d4515ffe35464 100644 --- a/docs/reference/elasticsearch/configuration-reference/node-settings.md +++ b/docs/reference/elasticsearch/configuration-reference/node-settings.md @@ -46,7 +46,10 @@ The following additional roles are available: * `voting_only` -$$$coordinating-only-node$$$If you leave `node.roles` unset, then the node is considered to be a [coordinating only node](docs-content://deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#coordinating-only-node-role). +$$$coordinating-only-node$$$If If you set `node.roles` to an empty array (`node.roles: [ ]`), then the node is considered to be a [coordinating only node](docs-content://deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#coordinating-only-node-role). + +[[coordinating-only-node]]If you set `node.roles` to an empty array (`node.roles: [ ]`), +then the node is considered to be a <>. ::::{important} If you set `node.roles`, ensure you specify every node role your cluster needs. Every cluster requires the following node roles: From 01a87511b22b180c84fffa5dae31423fe407b76e Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Tue, 4 Mar 2025 08:55:28 -0500 Subject: [PATCH 2/2] Update docs/reference/elasticsearch/configuration-reference/node-settings.md --- .../elasticsearch/configuration-reference/node-settings.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/reference/elasticsearch/configuration-reference/node-settings.md b/docs/reference/elasticsearch/configuration-reference/node-settings.md index d4515ffe35464..47f8fa18ff453 100644 --- a/docs/reference/elasticsearch/configuration-reference/node-settings.md +++ b/docs/reference/elasticsearch/configuration-reference/node-settings.md @@ -48,9 +48,6 @@ The following additional roles are available: $$$coordinating-only-node$$$If If you set `node.roles` to an empty array (`node.roles: [ ]`), then the node is considered to be a [coordinating only node](docs-content://deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#coordinating-only-node-role). -[[coordinating-only-node]]If you set `node.roles` to an empty array (`node.roles: [ ]`), -then the node is considered to be a <>. - ::::{important} If you set `node.roles`, ensure you specify every node role your cluster needs. Every cluster requires the following node roles: