Skip to content

Commit abb0ab0

Browse files
committed
[DOCS] Clarify connections and gateway nodes selection in cross cluster search docs (#24859)
Closes #24836
1 parent 05f340a commit abb0ab0

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/reference/modules/cross-cluster-search.asciidoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,12 @@ federated search requests.
1010

1111
Cross cluster search works by configuring a remote cluster in the cluster state and connecting only to a
1212
limited number of nodes in the remote cluster. Each remote cluster is referenced by a name and a list of seed nodes.
13-
Those seed nodes are used to discover nodes in the remote cluster which are eligible as _gateway nodes_.
13+
When a remote cluster is registered, its cluster state is retrieved from one of the seed nodes so that up to 3
14+
_gateway nodes_ are selected to be connected to as part of upcoming cross cluster search requests.
15+
Cross cluster search requests consist of uni-directional connections from the coordinating node to the previously
16+
selected remote nodes only. It is possible to tag which nodes should be selected through
17+
node attributes (see <<cross-cluster-search-settings>>).
18+
1419
Each node in a cluster that has remote clusters configured connects to one or more _gateway nodes_ and uses
1520
them to federate search requests to the remote cluster.
1621

@@ -172,6 +177,7 @@ will be prefixed with their remote cluster name:
172177
// TESTRESPONSE
173178

174179
[float]
180+
[[cross-cluster-search-settings]]
175181
=== Cross cluster search settings
176182

177183
`search.remote.connections_per_cluster`::

0 commit comments

Comments
 (0)