Delete a dangling index Generally available; Added in 7.9.0

DELETE /_dangling/{index_uuid}
Api key auth Basic auth Bearer auth

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

Path parameters

  • index_uuid string Required

    The UUID of the index to delete. Use the get dangling indices API to find the UUID.

Query parameters

  • accept_data_loss boolean Required

    This parameter must be set to true to acknowledge that it will no longer be possible to recove data from the dangling index.

  • master_timeout string

    Specify timeout for connection to master

    External documentation
  • timeout string

    Explicit operation timeout

    External documentation

Responses

  • 200 application/json
    Hide response attribute Show response attribute object
    • acknowledged boolean Required

      For a successful response, this value is always true. On failure, an exception is returned instead.
DELETE /_dangling/{index_uuid} 
DELETE /_dangling/<index-uuid>?accept_data_loss=true 
resp = client.dangling_indices.delete_dangling_index( index_uuid="<index-uuid>", accept_data_loss=True, )
const response = await client.danglingIndices.deleteDanglingIndex({ index_uuid: "<index-uuid>", accept_data_loss: "true", });
response = client.dangling_indices.delete_dangling_index( index_uuid: "<index-uuid>", accept_data_loss: "true" )
$resp = $client->danglingIndices()->deleteDanglingIndex([ "index_uuid" => "<index-uuid>", "accept_data_loss" => "true", ]);
curl -X DELETE -H "Authorization: ApiKey $ELASTIC_API_KEY" "$ELASTICSEARCH_URL/_dangling/<index-uuid>?accept_data_loss=true"