Import a dangling index
/_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
Parameters
path Path Parameters
| Name | Type |
|---|---|
index_uuid
required
The UUID of the index to import. Use the get dangling indices API to locate the UUID. | type TypesUuid = string |
query Query Parameters
| Name | Type |
|---|---|
accept_data_loss 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. | boolean |
master_timeout The period to wait for a connection to the master node. | type TypesDuration = string | "-1" | "0" |
timeout The period to wait for a response. | type TypesDuration = string | "-1" | "0" |
Responses
acknowledged: boolean;
}