anchor.diff:  processes is calculated automatically and takes into account the total node size
   and the size of the JVM on the node. The default value is `false`. If this
   setting differs between nodes, the value on the current master node is heeded.
  +When the {operator-feature} is enabled, this setting can be updated only by
  +operator users.
   +
   TIP: If you do not have dedicated {ml} nodes (that is to say, the node has
   multiple roles), do not enable this setting. Its calculations assume that {ml}
  
positive.code: cluster scaling. Defaults to `0b`, which means this value is ignored. If you set
  it to the maximum possible size of future {ml} nodes, when a {ml} job is
  assigned to a lazy node it can check (and fail quickly) when scaling cannot 
  support the size of the job. 
  
  `xpack.ml.process_connect_timeout`::
  (<<cluster-update-settings,Dynamic>>) The connection timeout for {ml} processes
  
negative.code: of nodes have already been provisioned. If a job is opened and this setting has
  a value greater than zero and there are no nodes that can accept the job, the
  job stays in the `OPENING` state until a new {ml} node is added to the cluster
  and the job is assigned to run on that node. When the {operator-feature} is
  enabled, this setting can be updated only by operator users.
  +
  IMPORTANT: This setting assumes some external process is capable of adding {ml}
  nodes to the cluster. This setting is only useful when used in conjunction with
  