- 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
Batch start or resume reindex API
editBatch start or resume reindex API
editThe underlying Upgrade Assistant concepts are stable, but the APIs for managing Upgrade Assistant are experimental.
Start or resume multiple reindexing tasks in one request. Additionally, reindexing tasks started or resumed via the batch endpoint will be placed on a queue and executed one-by-one, which ensures that minimal cluster resources are consumed over time.
Request
editPOST /api/upgrade_assistant/reindex/batch
Request body
edit-
indexNames
- (Required, array) The list of index names to be reindexed.
Response code
edit-
200
- Indicates a successful call.
Example
editSimilar to the start or resume endpoint, the API returns the following:
{ "enqueued": [ { "indexName": "index1", "newIndexName": "reindexed-v8-index1", "status": 3, "lastCompletedStep": 0, "locked": null, "reindexTaskId": null, "reindexTaskPercComplete": null, "errorMessage": null, "runningReindexCount": null, "reindexOptions": { "queueSettings": { "queuedAt": 1583406985489 } } } ], "errors": [ { "indexName": "index2", "message": "Something went wrong!" } ] }
A list of reindex tasks created, the order in the array indicates the order in which tasks will be executed. |
|
Presence of this key indicates that the reindex job will occur in the batch. |
|
A Unix timestamp of when the reindex task was placed in the queue. |
|
A list of errors that may have occurred preventing the reindex task from being created. |
On this page