Delete a dangling index

DELETE /_dangling/{index_uuid}

Copy endpoint

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.

Required authorization

Cluster privileges: manage

Parameters

path Path Parameters

Name	Type
`index_uuid` required The UUID of the index to delete. Use the get dangling indices API to find the UUID.	type TypesUuid = string

query Query Parameters

Name	Type
`accept_data_loss` This parameter must be set to true to acknowledge that it will no longer be possible to recove data from the dangling index.	boolean
`master_timeout` The period to wait for a connection to the master node.	type TypesDuration = string \| "-1" \| "0"
`timeout` The period to wait for a response.	type TypesDuration = string \| "-1" \| "0"

Responses

200 application/json

interface TypesAcknowledgedResponseBase {
acknowledged: boolean;
}