Delete dangling index APIedit

Deletes a dangling index.

Requestedit

DELETE /_dangling/<index-uuid>?accept_data_loss=true

Descriptionedit

If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more than cluster.indices.tombstones.size indices while an Elasticsearch node is offline.

Deletes a dangling index by referencing its UUID. Use the List dangling indices API to locate the UUID of an index.

Path parametersedit

<index-uuid>
(Required, string) UUID of the index to delete. You can find this using the List dangling indices API.

Query parametersedit

accept_data_loss
(Optional, boolean) This field must be set to true in order to carry out the import, since it will no longer be possible to recover the data from the dangling index.
master_timeout
(Optional, time units) Specifies the period of time to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error. Defaults to 30s.
timeout
(Optional, time units) Specifies the period of time to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Defaults to 30s.