This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
Start or resume reindex API
editStart or resume reindex API
editThe underlying Upgrade Assistant concepts are stable, but the APIs for managing Upgrade Assistant are experimental.
Start a new reindex or resume a paused reindex. Following steps are performed during a reindex task:
- Setting the index to read-only
- Creating a new index
- Reindexing documents into the new index
- Creating an index alias for the new index
- Deleting the old index
Request
editPOST <kibana host>:<port>/api/upgrade_assistant/reindex/myIndex
Response code
edit-
200
- Indicates a successful call.
Example
editThe API returns the following:
{ "indexName": ".ml-state", "newIndexName": ".reindexed-v7-ml-state", "status": 0, "lastCompletedStep": 0, "reindexTaskId": null, "reindexTaskPercComplete": null, "errorMessage": null }
The name of the new index. |
|
The reindex status. For more information, refer to Status codes. |
|
The last successfully completed step of the reindex. For more information, refer to Step codes. |
|
The task ID of the reindex task in Elasticsearch. Appears when the reindexing starts. |
|
The progress of the reindexing task in Elasticsearch. Appears in decimal form, from 0 to 1. |
|
The error that caused the reindex to fail, if it failed. |