Skip to content
This repository was archived by the owner on Dec 14, 2022. It is now read-only.

Commit f835a54

Browse files
author
Chris Wiechmann
authored
Update README.md
1 parent 655fb6a commit f835a54

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -904,7 +904,7 @@ For example, if you specify a maximum age and size for an index, then the index
904904
- If the maximum size is too small for your transaction volume, then an index can meet the size condition in less than 24 hours and will be rolled over.
905905
- If the maximum size is too large, the index will be rolled when it reaches the maximum age (e.g. after 7 days).
906906

907-
So how long the data is available from the very beginning to the end of an index is the sum of the period from the index's initial creation to the rollover __plus__ the period until the delete. As the rollover date cannot be defined exactly, you need to monitor your system accordingly and adjust the lifecycle accordingly to get the desired retention time.
907+
☝️ So how long the data is available from the very beginning to the end of an index is the sum of the period from the index's initial creation to the rollover plus the period until the delete. As the rollover date cannot be defined exactly, you need to monitor your system accordingly and adjust the lifecycle accordingly to get the desired retention time.
908908

909909
You can use the following conditions for the rollover:
910910
- `max_age`: Defines the maximum age of an index until it is rolled over

0 commit comments

Comments
 (0)