Get information about all currently running reindex tasks

  • GET /_reindex
Auth

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.

Required privileges

Cluster privileges monitor monitor_reindex manage_reindex

Query parameters

detailed boolean · default: false

If true, include detailed task status information in the response.

Response

application/json
reindex object[] required

The list of currently running reindex tasks.

id string required

The ID of the reindex task. The ID is assigned when the task was first created and remains the same across graceful shutdown relocations.

description string

A sanitized description of the reindex operation (source and destination indices, and optionally remote host info).

start_time_in_millis number required

The time at which the reindex task started, in milliseconds since the Unix epoch. Remains the same across graceful shutdown relocations.

start_time string

The time at which the reindex task started, as an ISO-8601 formatted string. Remains the same across graceful shutdown relocations. Only present when the request includes the ?human=true query parameter.

running_time string

The elapsed running time of the reindex task, including relocations, in a human-readable format. Only present when the request includes the ?human=true query parameter.

running_time_in_nanos number required

The elapsed running time of the reindex task, including relocations, in nanoseconds.

cancelled boolean required

Whether the reindex task has been cancelled.