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.
Response
-
reindexobjectrequired -
The list of currently running reindex tasks.
-
idstringrequired -
The ID of the reindex task. The ID is assigned when the task was first created and remains the same across graceful shutdown relocations.
-
descriptionstring -
A sanitized description of the reindex operation (source and destination indices, and optionally remote host info).
-
start_time_in_millisnumberrequired -
The time at which the reindex task started, in milliseconds since the Unix epoch. Remains the same across graceful shutdown relocations.
-
start_timestring -
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=truequery parameter. -
running_timestring -
The elapsed running time of the reindex task, including relocations, in a human-readable format. Only present when the request includes the
?human=truequery parameter. -
running_time_in_nanosnumberrequired -
The elapsed running time of the reindex task, including relocations, in nanoseconds.
-
statusobject -
The current progress of the reindex operation.
-
noopsnumberrequired -
The number of documents that were ignored because the script used for the reindex returned a
noopvalue forctx.op. -
requests_per_secondnumberrequired -
The number of requests per second effectively executed during the reindex.
-
retriesobjectrequired -
The number of retries attempted by reindex.
bulkis the number of bulk actions retried andsearchis the number of search actions retried. -
throttled_millisnumberrequired -
Number of milliseconds the request slept to conform to
requests_per_second. -
throttled_until_millisnumberrequired -
This field should always be equal to zero in a
_reindexresponse. It only has meaning when using the Task API, where it indicates the next time (in milliseconds since epoch) a throttled request will be executed again in order to conform torequests_per_second. -
task_failuresobject -
Per-task failures encountered while listing reindex tasks. Tasks that failed are not included in the
reindexarray.