Import a dangling index

POST /_dangling/{index_uuid}

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 import. Use the get dangling indices API to locate the UUID.

Query parameters

accept_data_loss boolean · 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_timeout string · default: 30s: The period to wait for a connection to the master node.
timeout string · default: 30s: The period to wait for a response.

Response

application/json

acknowledged boolean required: For a successful response, this value is always true. On failure, an exception is returned instead.