anchor.diff:  1. Take a snapshot to protect your data in case of disaster.
   
   2. Optionally, migrate the data away from the target node by using an
  -<<cluster-shard-allocation-filtering,allocation filter>>:
  +{ref}/modules-cluster.html#cluster-shard-allocation-filtering[allocation filter]:
   +
   [source,console]
   --------------------------------------------------
  
positive.code: }
  --------------------------------------------------
  +
  You can use the <<cat-allocation,cat allocation API>> to track progress of this
  data migration. If some shards do not migrate then the
  <<cluster-allocation-explain,cluster allocation explain API>> will help you to
  determine why.
  
  3. Follow the steps in the <<restart-cluster-rolling,rolling restart process>>
  up to and including shutting the target node down.
  
  4. Ensure your cluster health is `yellow` or `green`, so that there is a copy
  
negative.code: single machine then you must run one node for each data path.
  
  If you currently use multiple data paths in a
  {ref}/high-availability-cluster-design.html[highly available cluster] then you 
  can migrate to a setup that uses a single path for each node without downtime 
  using a process similar to a 
  {ref}/restart-cluster.html#restart-cluster-rolling[rolling restart]: shut each
  node down in turn and replace it with one or more nodes each configured to use
  a single data path. In more detail, for each node that currently has multiple
  data paths you should follow the following process. In principle you can
  