› › ›

Delete dangling index API

Deletes a dangling index.

Request

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

Prerequisites

If the Elasticsearch security features are enabled, you must have the manage cluster privilege to use this API.

Description

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 parameters

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

Query parameters

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) Period 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) Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Defaults to 30s.

© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/dangling-index-delete.html