anchor.diff:  === Cross cluster search settings
   
   * `search.remote.connections_per_cluster` - the number of nodes to connect to per remote cluster. The default is `3`
  -* `search.remote.initial_connect_timeout` - the time to wait for remote connections to be established when the node starts. The default is `30s`.
  -* `search.remote.node_attribute` - a node attribute to filter out nodes that are eligible as a gateway node in the remote cluster.
  -For instance a node can have a node attribute `node.attr.gateway: true`  such that only nodes with this attribute
  -will be connected to if `search.remote.node_attribute` is set to `gateway`
  +* `search.remote.initial_connect_timeout` - the time to wait for remote connections to be established when the node
  +starts. The default is `30s`.
  +* `search.remote.node_attribute` - a node attribute to filter out nodes that are eligible as a gateway node in the
  +remote cluster. For instance a node can have a node attribute `node.attr.gateway: true`  such that only nodes with this
  + attribute will be connected to if `search.remote.node_attribute` is set to `gateway`
   
  
positive.code: --------------------------------------------------
  
  Search results are disambiguated the same way as the indices are disambiguated in the request. Even if index names are
  identical these indices will be treated as different indices when results are merged. All results retrieved from a remote index
  will be prefixed with their remote cluster name:
  
  [source,js]
  
negative.code: }
  --------------------------------------------------
  
  In contrast to the `tribe` feature cross cluster search can also search indices with the same name on different
  clusters:
  
  [source,js]
  --------------------------------------------------
  