anchor.diff:  [[modules-remote-clusters]]
   == Remote clusters
   
  -The _remote clusters_ functionality enables you to establish unidirectional
  -connections to a remote cluster. Remote clusters are required for
  -<<xpack-ccr,{ccr}>> and <<modules-cross-cluster-search,{ccs}>>.
  -
  -Remote cluster connections work by configuring a remote cluster and connecting
  -to a limited number of nodes in that remote cluster. There are two modes for
  -remote cluster connections: <<sniff-mode,sniff mode>> and
  -<<proxy-mode,proxy mode>>.
  -
  -Communication with a remote cluster uses the <<modules-transport,transport
  -layer>> to establish a number of <<long-lived-connections,long-lived>> TCP
  -connections from the coordinating nodes of the local cluster to the chosen
  -nodes in the remote cluster.
  -
  -[discrete]
  +You can connect a local cluster to other {es} clusters, known as _remote
  +clusters_. Once connected, you can search remote clusters using
  +<<modules-cross-cluster-search,{ccs}>>. You can also sync data between clusters
  +using <<xpack-ccr,{ccr}>>.
  +
  +To register a remote cluster, connect the local cluster to nodes in the
  +remote cluster using one of two connection modes:
  +
  +* <<sniff-mode,Sniff mode>>
  +* <<proxy-mode,Proxy mode>>
  +
  +Your local cluster uses the <<modules-transport,transport layer>> to establish
  +communication with remote clusters. The coordinating nodes in the local cluster
  +establish <<long-lived-connections,long-lived>> TCP connections with specific
  +nodes in the remote cluster. {es} requires these connections to remain open,
  +even if the connections are idle for an extended period.
  +
  +You can use the <<cluster-remote-info, remote cluster info API>> to get
  +information about registered remote clusters.
  +
   [[sniff-mode]]
  -=== Sniff mode
  +[discrete]
  +==== Sniff mode
   
   In sniff mode, a cluster is created using a name and a list of seed nodes. When
   a remote cluster is registered, its cluster state is retrieved from one of the
  
positive.code: `cluster_one` and `cluster_three` intact.
  
  [discrete]
  [[remote-cluster-settings]]
  === Remote cluster settings for all modes
  
  These settings apply to both <<sniff-mode,sniff mode>> and
  <<proxy-mode,proxy mode>>. <<remote-cluster-sniff-settings,Sniff mode settings>>
  and <<remote-cluster-proxy-settings,proxy mode settings>> are described below.
  
  `cluster.remote.<cluster_alias>.mode`::
    The mode used for a remote cluster connection. The only supported modes are
  
negative.code: | 7.1->7.x      | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon}
  |====
  // end::remote-cluster-compatibility-matrix[]
  ====
  
  * *role*: Dedicated master nodes are never selected as gateway nodes.
  * *attributes*: You can tag which nodes should be selected
  (see <<remote-cluster-settings>>), though such tagged nodes still have
  to satisfy the two above requirements.
  
  [[proxy-mode]]
  [discrete]
  ==== Proxy mode
  
  In proxy mode, a cluster is created using a name and a single proxy address.
  When you register a remote cluster, a configurable number of socket connections
  are opened to the proxy address. The proxy is required to route those
  connections to the remote cluster. Proxy mode does not require remote cluster
  nodes to have accessible publish addresses.
  
  The proxy mode is not the default connection mode and must be configured. Similar
  to the sniff <<gateway-nodes-selection,gateway nodes>>, the remote
  