|
2 | 2 | == Remote clusters
|
3 | 3 |
|
4 | 4 | ifndef::include-xpack[]
|
5 |
| -The _remote clusters_ module allows establishing uni-directional connections to |
6 |
| -a remote cluster. This functionality is used in |
| 5 | +The _remote clusters_ module enables you to establish uni-directional |
| 6 | +connections to a remote cluster. This functionality is used in |
7 | 7 | <<modules-cross-cluster-search,cross-cluster search>>.
|
8 | 8 | endif::[]
|
9 | 9 | ifdef::include-xpack[]
|
10 |
| -The _remote clusters_ module allows establishing uni-directional connections to |
11 |
| -a remote cluster. This functionality is used in cross-cluster replication, and |
| 10 | +The _remote clusters_ module enables you to establish uni-directional |
| 11 | +connections to a remote cluster. This functionality is used in |
| 12 | +{stack-ov}/xpack-ccr.html[cross-cluster replication] and |
12 | 13 | <<modules-cross-cluster-search,cross-cluster search>>.
|
13 | 14 | endif::[]
|
14 | 15 |
|
15 | 16 | Remote cluster connections work by configuring a remote cluster and connecting
|
16 | 17 | only to a limited number of nodes in the remote cluster. Each remote cluster is
|
17 |
| -referenced by a name and a list of seed nodes. When a remote cluster is |
| 18 | +referenced by a name and a list of seed nodes. When a remote cluster is |
18 | 19 | registered, its cluster state is retrieved from one of the seed nodes so that by
|
19 | 20 | default up to three _gateway nodes_ are selected to be connected to as part of
|
20 | 21 | remote cluster requests. Remote cluster connections consist of uni-directional
|
21 | 22 | connections from the coordinating node to the previously selected remote nodes
|
22 |
| -only. It is possible to tag which nodes should be selected through node |
23 |
| -attributes (see <<remote-cluster-settings>>). |
| 23 | +only. You can tag which nodes should be selected by using node attributes (see <<remote-cluster-settings>>). |
24 | 24 |
|
25 | 25 | Each node in a cluster that has remote clusters configured connects to one or
|
26 | 26 | more _gateway nodes_ and uses them to federate requests to the remote cluster.
|
@@ -173,6 +173,6 @@ PUT _cluster/settings
|
173 | 173 | [[retrieve-remote-clusters-info]]
|
174 | 174 | === Retrieving remote clusters info
|
175 | 175 |
|
176 |
| -The <<cluster-remote-info, Remote Cluster Info API>> allows to retrieve |
| 176 | +You can use the <<cluster-remote-info, remote cluster info API>> to retrieve |
177 | 177 | information about the configured remote clusters, as well as the remote nodes
|
178 | 178 | that the node is connected to.
|
0 commit comments