Get information about all currently running reindex tasks

GET /_reindex

Reindex tasks that are mid-relocation between nodes are reported once, under their original task ID, so callers do not see duplicates across the relocation chain.

If the API returns a HTTP status of 200 OK, but node_failures or task_failures are non-empty in the body, the listing is not a complete authoritative listing and may be missing tasks.

Query Parameters

detailed boolean · default: false: If true, include detailed task status information in the response.

Response

application/json

Examples

A successful response from GET _reindex listing a single currently running reindex task.

Request Console 1 / 8 languages

Console Kibana Dev Tools

GET _reindex

JavaScript Elasticsearch JavaScript Client

const response = await client.listReindex();

Python Elasticsearch Python Client

resp = client.list_reindex()

curl Shell

curl -X GET "$ELASTICSEARCH_URL/_reindex" \
  -H "Authorization: ApiKey $ELASTIC_API_KEY"

Java Elasticsearch Java Client

client.listReindex(l -> l);

C# Elasticsearch .NET Client

var response = await client.ListReindexAsync();

PHP Elasticsearch PHP Client

$resp = $client->listReindex();

Ruby Elasticsearch Ruby Client

response = client.list_reindex

Response

{
  "reindex": [
    {
      "id": "r1A2WoRbTwKZ516z6NEs5A:36619",
      "start_time_in_millis": 1762190000000,
      "running_time_in_nanos": 4200000000,
      "cancelled": false
    }
  ]
}