anchor.diff:      that these implications are well-understood, this command requires the flag
       `accept_data_loss` to be explicitly set to `true`.
   
  +
  +[[cluster-reroute-api-example]]
  +==== {api-examples-title}
  +
  +This is a short example of a simple reroute API call:
  +
  +[source,js]
  +--------------------------------------------------
  +POST /_cluster/reroute
  +{
  +    "commands" : [
  +        {
  +            "move" : {
  +                "index" : "test", "shard" : 0,
  +                "from_node" : "node1", "to_node" : "node2"
  +            }
  +        },
  +        {
  +          "allocate_replica" : {
  +                "index" : "test", "shard" : 1,
  +                "node" : "node3"
  +          }
  +        }
  +    ]
  +}
  +--------------------------------------------------
  +// CONSOLE
  +// TEST[skip:doc tests run with only a single node]
  
positive.code: If the `?explain` URI query parameter is included then a detailed explanation
  of why the commands could or could not be executed is included in the response.
  
  The commands supported are:
  
  `move`::
      Move a started shard from one node to another node. Accepts
      `index` and `shard` for index name and shard number, `from_node` for the
      node to move the shard from, and `to_node` for the node to move the
      shard to.
  
  `cancel`::
      Cancel allocation of a shard (or recovery). Accepts `index` and `shard` for
  
negative.code:     Allocate an unassigned replica shard to a node. Accepts `index` and `shard`
      for index name and shard number, and `node` to allocate the shard to. Takes
      <<modules-cluster,allocation deciders>> into account.
  --
  
  Two more commands are available that allow the allocation of a primary shard to
  a node. These commands should however be used with extreme care, as primary
  shard allocation is usually fully automatically handled by {es}. Reasons why a 
  primary shard cannot be automatically allocated include the
  following:
  
  - A new index was created but there is no node which satisfies the allocation
  