anchor.diff:      already used by the running relocation.
   
   
  -An example of updating the low watermark to no more than 80% of the disk size, a
  -high watermark of at least 50 gigabytes free, and updating the information about
  -the cluster every minute:
  +NOTE: Percentage values refer to used disk space, while byte values refer to
  +free disk space. This can be confusing, since it flips the meaning of high and
  +low. For example, it makes sense to set the low watermark to 10gb and the high
  +watermark to 5gb, but not the other way around.
  +
  +
  +An example of updating the low watermark to no more than 80% of the disk size,
  +a high watermark of at least 50 gigabytes free, and a floodstage watermark of
  +10 gigabytes free, and updating the information about the cluster every
  +minute:
   
   [source,js]
   --------------------------------------------------
  
positive.code: --------------------------------------------------
  // CONSOLE
  // TEST[setup:twitter]
  
  
  NOTE: Percentage values refer to used disk space, while byte values refer to
  free disk space. This can be confusing, since it flips the meaning of high and
  low. For example, it makes sense to set the low watermark to 10gb and the high
  watermark to 5gb, but not the other way around.
  
  
  `cluster.info.update.interval`::
  
  
negative.code:     the node.
  
  `cluster.routing.allocation.disk.watermark.floodstage`::
  +
  --
      Controls the floodstage watermark. It defaults to 95%, meaning ES enforces a read-only
      index block (`index.blocks.read_only_allow_delete`) on every index that has
      one or more shards allocated on the node that has at least one disk exceeding the floodstage.
      This is a last resort to prevent nodes from running out of disk space.
      The index block must be released manually once there is enough disk space available
      to allow indexing operations to continue.
  