anchor.diff:  // TEST[s/127.0.0.1:9300/\${transport_host}/]
   
   You can dynamically update the compression and ping schedule settings. However,
  -you must re-include seeds or `proxy_address` in the settings update request.
  +you must include the `seeds` or `proxy_address` in the settings update request.
   For example:
   
   [source,console]
  
positive.code: `cluster.remote.<cluster_alias>.transport.ping_schedule`::
  
    Sets the time interval between regular application-level ping messages that
    are sent to ensure that transport connections to nodes belonging to remote
    clusters are kept alive. If set to `-1`, application-level ping messages to
    this remote cluster are not sent. If unset, application-level ping messages
    are sent according to the global `transport.ping_schedule` setting, which
    defaults to `-1` meaning that pings are not sent.
  
  `cluster.remote.<cluster_alias>.transport.compress`::
  
  
negative.code:           "mode": null,
            "seeds": null,
            "skip_unavailable": null,
            "transport.compress": null
          }
        }
      }
  