- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.3
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Enterprise Search settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Monitoring settings
- Reporting settings
- Search sessions settings
- Secure settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure logging
- Configure monitoring
- Command line tools
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Data views API
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Cases APIs
- Import and export dashboard APIs
- Logstash configuration management APIs
- Machine learning APIs
- Short URLs APIs
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Troubleshooting
- Accessibility
- Release notes
- Developer guide
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. |
On this page