anchor.diff:  
   
   [[cluster-reroute-api-query-params]]
  +[role="child_attributes"]
   ==== {api-query-parms-title}
   
   `dry_run`::
  -    (Optional, boolean) If `true`, then the request simulates the operation only 
  +    (Optional, boolean) If `true`, then the request simulates the operation only
       and returns the resulting state.
  -    
  +
   `explain`::
  -    (Optional, boolean) If `true`, then the response contains an explanation of 
  +    (Optional, boolean) If `true`, then the response contains an explanation of
       why the commands can or cannot be executed.
   
   `metric`::
  -    (Optional, string) Limits the information returned to the specified metrics. 
  +    (Optional, string) Limits the information returned to the specified metrics.
       Defaults to all but metadata The following options are available:
   
   +
  ---
  +.Options for `metric`
  +[%collapsible%open]
  +======
   `_all`::
       Shows all metrics.
  -        
  +
   `blocks`::
       Shows the `blocks` part of the response.
   
   `master_node`::
       Shows the elected `master_node` part of the response.
  -        
  +
   `metadata`::
       Shows the `metadata` part of the response. If you supply a comma separated
       list of indices, the returned output will only contain metadata for these
  
positive.code: 
  `routing_table`::
      Shows the `routing_table` part of the response.
          
  `version`::
      Shows the cluster state version.
  --
  
  `retry_failed`::
      (Optional, boolean) If `true`, then retries allocation of shards that are 
      blocked due to too many subsequent allocation failures.
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
  
  
  [[cluster-reroute-api-request-body]]
  ==== {api-request-body-title}
  
  `commands`::
      (Required, object) Defines the commands to perform. Supported commands 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`::
  
negative.code:     data rejoins the cluster later on, that data will be deleted. To ensure
      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}
  