anchor.diff:  
   [discrete]
   [[configuring-remote-clusters]]
  -==== Configuring remote clusters
  -
  -You can configure remote clusters globally by using
  -<<cluster-update-settings,cluster settings>>, which you can update dynamically.
  -Alternatively, you can configure them locally on individual nodes by using the
  - `elasticsearch.yml` file.
  -
  -If you specify the settings in `elasticsearch.yml` files, only the nodes with
  -those settings can connect to the remote cluster. In other words, functionality
  -that relies on remote cluster requests must be driven specifically from those
  -nodes. For example:
  -
  -[source,yaml]
  ---------------------------------
  -cluster:
  -    remote:
  -        cluster_one: <1>
  -            seeds: 127.0.0.1:9300 <2>
  -            transport.ping_schedule: 30s <3>
  -        cluster_two: <1>
  -            mode: sniff <4>
  -            seeds: 127.0.0.1:9301 <2>
  -            transport.compress: true <5>
  -            skip_unavailable: true <6>
  -        cluster_three: <1>
  -            mode: proxy <4>
  -            proxy_address: 127.0.0.1:9302 <7>
  -
  ---------------------------------
  -<1> `cluster_one`, `cluster_two`, and `cluster_three` are arbitrary _cluster aliases_
  -representing the connection to each cluster. These names are subsequently used to
  -distinguish between local and remote indices.
  -<2> The hostname and <<modules-transport,transport>> port (default: 9300) of a
  -seed node in the remote cluster.
  -<3> A keep-alive ping is configured for `cluster_one`.
  -<4> The configured connection mode. By default, this is <<sniff-mode,`sniff`>>, so
  -the mode is implicit for `cluster_one`. However, it can be explicitly configured
  -as demonstrated by `cluster_two` and must be explicitly configured for
  -<<proxy-mode,proxy mode>> as demonstrated by `cluster_three`.
  -<5> Compression is explicitly enabled for requests to `cluster_two`.
  -<6> Disconnected remote clusters are optional for `cluster_two`.
  -<7> The address for the proxy endpoint used to connect to `cluster_three`.
  -
  -For more information about the optional transport settings, see
  -<<modules-transport>>.
  -
  -
  -If you use <<cluster-update-settings,cluster settings>>, the remote clusters
  -are available on every node in the cluster. For example:
  +=== Configuring remote clusters
  +
  +You can configure remote clusters settings <<configure-remote-clusters-dynamic,globally>>, or configure
  +settings <<configure-remote-clusters-static,on individual nodes>> in the
  +`elasticsearch.yml` file.
  +
  +[discrete]
  +[[configure-remote-clusters-dynamic]]
  +===== Dynamically configure remote clusters
  +Use the <<cluster-update-settings,cluster update settings API>> to dynamically
  +configure remote settings on every node in the cluster. For example:
   
   [source,console]
   --------------------------------
  
positive.code: 
  [discrete]
  [[remote-cluster-proxy-settings]]
  === Remote cluster settings for proxy mode
  
  `cluster.remote.<cluster_alias>.proxy_address`::
  
  
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
  