Get the status and progress of a specific reindex task
- GET /_reindex/{task_id}
This API follows reindex tasks across node-shutdown relocations, so callers can keep using the original task ID throughout the lifetime of the operation. Returned task IDs and timings reflect the original task, not its relocated successor. Relocated task IDs are also supported. They are followed transparently and return the task ID and timings of the original task.
When the task ID cannot be resolved, the API returns the response below with a 404 status code. This response is used whether the ID is unknown, refers to a non-reindex task, refers to a sliced child subtask, or refers to a task whose node left the cluster with no stored result (e.g. a non-graceful shutdown).
{
"error": {
"type": "resource_not_found_exception",
"reason": "Reindex operation [r1A2WoRbTwKZ516z6NEs5A:36619] not found"
},
"status": 404
}
Response
-
idstringrequired -
The ID of the reindex task. The value is the ID assigned when the task was first created and remains stable across node-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.
-
start_timestring -
The time at which the reindex task started, as an ISO 8601 formatted string. Only present when the request includes the
?human=truequery parameter. -
running_timestring -
The elapsed running time of the reindex task, in a human-readable format. Only present when the request includes the
?human=truequery parameter. -
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. -
responseobject -
The final result of the completed reindex operation, if the task has finished successfully.
-
failuresobject -
Any failures encountered during the reindex. If non-empty, the reindex ended because of these failures.
-
noopsnumber -
The number of documents that were ignored because the script returned a
noopvalue forctx.op. -
requests_per_secondnumber -
The number of requests per second effectively executed during the reindex.