anchor.diff:  Closed indices consume a significant amount of disk-space which can cause problems in managed environments. Closing indices can be disabled via the cluster settings
   API by setting `cluster.indices.close.enable` to `false`. The default is `true`.
   
  -[float]
  -==== Wait For Active Shards
  +===== Wait For active shards
   
   Because opening or closing an index allocates its shards, the
   <<create-index-wait-for-active-shards,`wait_for_active_shards`>> setting on
   index creation applies to the `_open` and `_close` index actions as well.
  +
  +// end:closed-index
  +
  +
  +[[open-index-api-path-params]]
  +==== {api-path-parms-title}
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=index]
  ++
  +To open all indices, use `_all` or `*`.
  +To disallow the opening of indices with `_all` or wildcard expressions,
  +change the `action.destructive_requires_name` cluster setting to `true`.
  +You can update this setting in the `elasticsearch.yml` file
  +or using the <<cluster-update-settings,cluster update settings>> API.
  +
  +
  +[[open-index-api-query-params]]
  +==== {api-query-parms-title}
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
  ++
  +Defaults to `closed`.
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=doc-wait-for-active-shards]
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
  +
  +
  +[[open-index-api-example]]
  +==== {api-examples-title}
  +
  +A closed index can be re-opened like this:
  +
  +[source,js]
  +--------------------------------------------------
  +POST /my_index/_open
  +--------------------------------------------------
  +// CONSOLE
  +// TEST[s/^/PUT my_index\nPOST my_index\/_close\n/]
  +
  +The API returns the following response:
  +
  +[source,js]
  +--------------------------------------------------
  +{
  +    "acknowledged" : true,
  +    "shards_acknowledged" : true
  +}
  +--------------------------------------------------
  +// TESTRESPONSE
  
positive.code: [[indices-open-close]]
  === Open / Close Index API
  
  The open and close index APIs allow to close an index, and later on
  opening it.
  
  A closed index is blocked for read/write operations and does not allow
  all operations that opened indices allow. It is not possible to index
  
negative.code: cluster to ensure that enough shard copies are safely kept around
  at all times.
  
  You can open and close multiple indices. An error is thrown
  if the request explicitly refers to a missing index. This behaviour can be
  disabled using the `ignore_unavailable=true` parameter.
  
  