After you enable the scenario-based configuration feature, you can use the related template to modify the index lifecycle configurations of a cluster. This topic describes how to modify the index lifecycle configurations of a cluster.
For more information about how to modify the index lifecycle configurations of a cluster,
see Use a scenario-based template to modify the configurations of a cluster. The following table describes the related parameters.
Notice
You can use the related template to modify the index lifecycle configurations of an Alibaba Cloud Elasticsearch cluster of V6.7 or later that has warm nodes.
The policy defined in the default index lifecycle template is named aliyun_default_ilm_policy. This policy is already applied to aliyun_default_index_template.
| Parameter | Description |
|---|---|
phases.hot.min_age |
The time required for an index to enter the hot phase. |
phases.hot.actions.set_priority.priority |
The priority of an index in the hot phase. |
phases.warm.min_age |
The time required for an index to enter the warm phase. |
phases.warm.actions.allocate.number_of_replicas |
The number of replica shards for an index in the warm phase. |
phases.warm.actions.allocate.require.box_type |
The shard allocation policy in the warm phase. For example, the system allocates shards to warm nodes. |
phases.warm.actions.set_priority.priority |
The priority of an index in the warm phase. |
phases.cold.min_age |
The time required for an index to enter the cold phase. |
phases.cold.actions.set_priority.priority |
The priority of an index in the cold phase. |