anchor.diff:  
   NOTE: Mappings may not be specified in the `_shrink` request.
   
  -[float]
  -==== Monitoring the shrink process
  +
  +[[monitor-shrink]]
  +===== Monitor the shrink process
   
   The shrink process can be monitored with the <<cat-recovery,`_cat recovery`
   API>>, or the <<cluster-health, `cluster health` API>> can be used to wait
  
positive.code: 
  [source,console]
  --------------------------------------------------
  POST my_source_index/_shrink/my_target_index
  {
    "settings": {
      "index.number_of_replicas": 1,
  
negative.code: become `active`. At that  point, Elasticsearch will try to allocate any
  replicas and may decide to relocate the primary shard to another node.
  
  
  [[shrink-wait-active-shards]]
  ===== Wait for active shards
  
  Because the shrink operation creates a new index to shrink the shards to,
  the <<create-index-wait-for-active-shards,wait for active shards>> setting
  on index creation applies to the shrink index action as well.
  
  
  [[shrink-index-api-path-params]]
  ==== {api-path-parms-title}
  
  `<index>`::
  (Required, string)
  Name of the source index to shrink.
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=target-index]
  
  [[shrink-index-api-query-params]]
  ==== {api-query-parms-title}
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
  
  
  [[shrink-index-api-request-body]]
  ==== {api-request-body-title}
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=target-index-aliases]
  
  include::{docdir}/rest-api/common-parms.asciidoc[tag=target-index-settings]
  