anchor.diff:  [[node-ingest-node-setting]]
   // tag::node-ingest-tag[]
   `node.ingest` {ess-icon}::
  -Determines whether a node is an ingest node. <<ingest,Ingest nodes>> can apply an ingest pipeline to transform and enrich a document before indexing. Default: `true`.
  +Determines whether a node is an ingest node. <<ingest,Ingest nodes>> can apply 
  +an ingest pipeline to transform and enrich a document before indexing. Default: 
  +`true`.
   // end::node-ingest-tag[]
   
   [[coordinating-only-node]]
  
positive.code: nodes which hold the data.  Each data node executes the request locally and
  returns its results to the coordinating node. In the _gather_  phase, the
  coordinating node reduces each data node's results into a single global
  resultset.
  
  Every node is implicitly a coordinating node. This means that a node that has
  an explicit empty list of roles via `node.roles` will only act as a coordinating
  
negative.code: unexpected data then it will refuse to start. This is to avoid importing
  unwanted <<modules-gateway-dangling-indices,dangling indices>> which can lead
  to a red cluster health. To be more precise, nodes without the `data` role will
  refuse to start if they find any shard data on disk at startup, and nodes 
  without both the `master` and `data` roles will refuse to start if they have any 
  index metadata on disk at startup.
  
  It is possible to change the roles of a node by adjusting its
  `elasticsearch.yml` file and restarting it. This is known as _repurposing_ a
  