anchor.diff:  node connections must close and re-open, which can cause in-flight requests to
   fail.
   
  -A remote cluster can be deleted from the cluster settings by setting its seeds
  -to `null`:
  +A remote cluster can be deleted from the cluster settings by setting its seeds and optional settings to `null` :
   
   [source,js]
   --------------------------------
  
positive.code: between local and remote indices.
  <2> A keep-alive ping is configured for `cluster_one`.
  <3> Compression is explicitly enabled for requests to `cluster_two`.
  
  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:
  
negative.code:   "persistent": {
      "cluster": {
        "remote": {
          "cluster_two": { <1>
            "seeds": null,
            "skip_unavailable": null,
            "transport": {
              "compress": null
            }
          }
        }
      }
  