anchor.diff:  {kibana-ref}/ml-settings-kb.html[{kib} {ml} settings].
   +
   IMPORTANT: If you want to use {ml-features} in your cluster, it is recommended
  -that you set `xpack.ml.enabled` to `true` on all nodes. This is the
  -default behavior. At a minimum, it must be enabled on all master-eligible nodes.
  -If you want to use {ml-features} in clients or {kib}, it must also be enabled on
  -all coordinating nodes.
  +that you set `xpack.ml.enabled` to `true` on all nodes. This is the default 
  +behavior. At a minimum, it must be enabled on all master-eligible nodes. If you 
  +want to use {ml-features} in clients or {kib}, it must also be enabled on all 
  +coordinating nodes.
   
   `xpack.ml.inference_model.cache_size`::
   The maximum inference cache size allowed. The inference cache exists in the JVM
  
positive.code: [[general-ml-settings]]
  ==== General machine learning settings
  
  `node.ml`::
  deprecated:[7.9.0,"Use <<modules-node,node.roles>> instead."]
  Set to `true` (default) to identify the node as a _machine learning node_. +
  +
  If set to `false` in `elasticsearch.yml`, the node cannot run jobs. If set to
  `true` but `xpack.ml.enabled` is set to `false`, the `node.ml` setting is
  ignored and the node cannot run jobs. If you want to run jobs, there must be at
  least one machine learning node in your cluster. +
  +
  IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, disable
  the `node.ml` role.
  
  `xpack.ml.enabled`::
  Set to `true` (default) to enable {ml} on the node.
  +
  If set to `false`, the {ml} APIs are disabled on the node. Therefore the node
  cannot open jobs, start {dfeeds}, or receive transport (internal) communication
  
negative.code: run {es} on older hardware you must disable {ml} (by setting `xpack.ml.enabled`
  to `false`).
  
  All of these settings can be added to the `elasticsearch.yml` configuration 
  file. The dynamic settings can also be updated across a cluster with the
  <<cluster-update-settings,cluster update settings API>>. Dynamic settings take 
  precedence over settings in the `elasticsearch.yml` file.
  
  // end::ml-settings-description-tag[]
  
  