Skip to content

Commit 856c9b7

Browse files
committed
improve screenshot; add downsample graphic
1 parent a026aa4 commit 856c9b7

File tree

3 files changed

+5
-1
lines changed

3 files changed

+5
-1
lines changed
118 KB
Loading
15.4 KB
Loading

manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,11 @@ To add an ILM policy to an {{es}} cluster:
6565
The rollover action implicitly always rolls over a data stream or alias if one or more shards contain 200000000 or more documents. Normally a shard will reach 25GB long before it reaches 200M documents, but this isn’t the case for space efficient data sets. Search performance will very likely suffer if a shard contains more than 200M documents. This is the reason for the built-in limit.
6666
::::
6767

68-
1. By default, only the "hot" index lifecycle phase is enabled. Enable each additional lifecycle phase that you'd like, and for each choose any [index lifecycle actions](elasticsearch://reference/elasticsearch/index-lifecycle-actions/index.md) to perform on indices when they enter that phase. For example, you could choose the action to [downsample](/manage-data/data-store/data-streams/downsampling-time-series-data-stream.md) the index, which aggregates the time series data into statistical summaries, effectively reducing the data footprint.
68+
1. By default, only the "hot" index lifecycle phase is enabled. Enable each additional lifecycle phase that you'd like, and for each choose any [index lifecycle actions](elasticsearch://reference/elasticsearch/index-lifecycle-actions/index.md) to perform on indices when they enter that phase.
69+
70+
For example, you could choose the action to [downsample](/manage-data/data-store/data-streams/downsampling-time-series-data-stream.md) the index, which aggregates the time series data into statistical summaries, reducing the data storage size.
71+
72+
![Create policy page](/manage-data/images/elasticsearch-reference-create-policy-downsample.png "")
6973

7074
Note that for each phase after the "hot" phase you have the option to move the data into the phase after a certain duration of time. This duration is calculated from the time of the index rollover and not from the time the index is created.
7175

0 commit comments

Comments
 (0)