Browse Source

Reflect cross-cluster search in "dedicated" terminology (#23771)

* Reflects cross-cluster search in dedicated node settings

* Fix space issue
Shane Connelly 8 years ago
parent
commit
16a8d5245f
1 changed files with 5 additions and 1 deletions
  1. 5 1
      docs/reference/modules/node.asciidoc

+ 5 - 1
docs/reference/modules/node.asciidoc

@@ -209,10 +209,12 @@ To create a dedicated ingest node, set:
 node.master: false <1>
 node.data: false <2>
 node.ingest: true <3>
+search.remote.connect: false <4>
 -------------------
 <1> Disable the `node.master` role (enabled by default).
 <2> Disable the `node.data` role (enabled by default).
 <3> The `node.ingest` role is enabled by default.
+<4> Disable cross-cluster search (enabled by default).
 
 [float]
 [[coordinating-only-node]]
@@ -235,17 +237,19 @@ acknowledgement of cluster state updates from every node! The benefit of
 coordinating only nodes should not be overstated -- data nodes can happily
 serve the same purpose.
 
-To create a coordinating only node, set:
+To create a dedicated coordinating node, set:
 
 [source,yaml]
 -------------------
 node.master: false <1>
 node.data: false <2>
 node.ingest: false <3>
+search.remote.connect: false <4>
 -------------------
 <1> Disable the `node.master` role (enabled by default).
 <2> Disable the `node.data` role (enabled by default).
 <3> Disable the `node.ingest` role (enabled by default).
+<4> Disable cross-cluster search (enabled by default).
 
 [float]
 == Node data path settings