Import a dangling index
- POST /_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.
- Cluster privileges:
manage
Path Parameters
-
index_uuidstringrequired -
The UUID of the index to import. Use the get dangling indices API to locate the UUID.
Query Parameters
-
accept_data_lossboolean · default: false This parameter must be set to true to import a dangling index. Because Elasticsearch cannot know where the dangling index data came from or determine which shard copies are fresh and which are stale, it cannot guarantee that the imported data represents the latest state of the index when it was last in the cluster.
-
master_timeoutstring Duration · default: 30s The period to wait for a connection to the master node.
-
timeoutstring Duration · default: 30s The period to wait for a response.
Response
-
acknowledgedbooleanrequired -
For a successful response, this value is always true. On failure, an exception is returned instead.