Index lifecycle actions
- Allocate
- Move shards to nodes with different performance characteristics and reduce the number of replicas.
- Delete
- Permanently remove the index.
- Force merge
- Reduce the number of index segments and purge deleted documents. Makes the index read-only.
- Freeze
- Freeze the index to minimize its memory footprint.
- Migrate
- Move the index shards to the data tier that corresponds to the current ILM phase.
- Read only
- Block write operations to the index.
- Rollover
- Remove the index as the write index for the rollover alias and start indexing to a new index.
- Searchable snapshot
- Take a snapshot of the managed index in the configured repository and mount it as a searchable snapshot.
- Set priority
- Lower the priority of an index as it moves through the lifecycle to ensure that hot indices are recovered first.
- Shrink
- Reduce the number of primary shards by shrinking the index into a new index.
- Unfollow
- Convert a follower index to a regular index. Performed automatically before a rollover, shrink, or searchable snapshot action.
- Wait for snapshot
- Ensure that a snapshot exists before deleting the index.
© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/ilm-actions.html
