Import a dangling index Added in 7.9.0
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.
Path parameters
-
The UUID of the index to import. Use the get dangling indices API to locate the UUID.
Query parameters
-
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
Specify timeout for connection to master
-
timeout string
Explicit operation timeout
POST /_dangling/{index_uuid}
curl \
-X POST http://api.example.com/_dangling/{index_uuid}?accept_data_loss=true
Response examples (200)
{
"acknowledged": true
}