Delete a dangling index

DELETE /_dangling/{index_uuid}

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

Response

application/json

Examples

Request Console 1 / 7 languages

Console Kibana Dev Tools

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

JavaScript Elasticsearch JavaScript Client

const response = await client.danglingIndices.deleteDanglingIndex({
  index_uuid: "<index-uuid>",
  accept_data_loss: "true",
});

Python Elasticsearch Python Client

resp = client.dangling_indices.delete_dangling_index(
    index_uuid="<index-uuid>",
    accept_data_loss=True,
)

curl Shell

curl -X DELETE "$ELASTICSEARCH_URL/_dangling/<index-uuid>?accept_data_loss=true" \
  -H "Authorization: ApiKey $ELASTIC_API_KEY"

Java Elasticsearch Java Client

client.danglingIndices().deleteDanglingIndex(d -> d
    .acceptDataLoss(true)
    .indexUuid("<index-uuid>")
);

PHP Elasticsearch PHP Client

$resp = $client->danglingIndices()->deleteDanglingIndex([
    "index_uuid" => "<index-uuid>",
    "accept_data_loss" => "true",
]);

Ruby Elasticsearch Ruby Client

response = client.dangling_indices.delete_dangling_index(
  index_uuid: "<index-uuid>",
  accept_data_loss: "true"
)

Response

No example

Required authorization

Path Parameters

Query Parameters { accept_data_loss , master_timeout , timeout , }

Response

Query Parameters