Skip to content

Commit

Permalink
Updated ilm docs as per the issue (#118148)
Browse files Browse the repository at this point in the history
This PR updates the Elasticsearch ILM tutorial for the newer screenshot
and the primary shard update in the text.
  • Loading branch information
satyyam11 authored and dakrone committed Dec 17, 2024
1 parent 31aceb3 commit 19903d5
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/reference/ilm/example-index-lifecycle-policy.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ and retention requirements.
You want to send log files to an {es} cluster so you can visualize and analyze
the data. This data has the following retention requirements:

* When the write index reaches 50GB or is 30 days old, roll over to a new index.
* When the primary shard size of the write index reaches 50GB or the index is 30 days old, roll over to a new index.
* After rollover, keep indices in the hot data tier for 30 days.
* 30 days after rollover:
** Move indices to the warm data tier.
Expand Down Expand Up @@ -84,7 +84,7 @@ To save the `logs@lifecycle` policy as a new policy in {kib}:
. On the **Edit policy logs** page, toggle **Save as new policy**, and then provide a new name for the policy, for example, `logs-custom`.

The `logs@lifecycle` policy uses the recommended rollover defaults: Start writing to a new
index when the current write index reaches 50GB or becomes 30 days old.
index when the primary shard size of the current write index reaches 50GB or the index becomes 30 days old.

To view or change the rollover settings, click **Advanced settings** for the hot
phase. Then disable **Use recommended defaults** to display the rollover
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 19903d5

Please sign in to comment.