|
@@ -51,7 +51,7 @@ and the actions to perform in each phase. A lifecycle can have up to five phases
|
|
|
For example, you might define a `timeseries_policy` that has two phases:
|
|
|
|
|
|
* A `hot` phase that defines a rollover action to specify that an index rolls over when it
|
|
|
-reaches either a `max_size` of 50 gigabytes or a `max_age` of 30 days.
|
|
|
+reaches either a `max_primary_shard_size` of 50 gigabytes or a `max_age` of 30 days.
|
|
|
* A `delete` phase that sets `min_age` to remove the index 90 days after rollover.
|
|
|
Note that this value is relative to the rollover time, not the index creation time.
|
|
|
|
|
@@ -72,18 +72,18 @@ PUT _ilm/policy/timeseries_policy
|
|
|
{
|
|
|
"policy": {
|
|
|
"phases": {
|
|
|
- "hot": { <1>
|
|
|
+ "hot": { <1>
|
|
|
"actions": {
|
|
|
"rollover": {
|
|
|
- "max_size": "50GB", <2>
|
|
|
+ "max_primary_shard_size": "50GB", <2>
|
|
|
"max_age": "30d"
|
|
|
}
|
|
|
}
|
|
|
},
|
|
|
"delete": {
|
|
|
- "min_age": "90d", <3>
|
|
|
+ "min_age": "90d", <3>
|
|
|
"actions": {
|
|
|
- "delete": {} <4>
|
|
|
+ "delete": {} <4>
|
|
|
}
|
|
|
}
|
|
|
}
|
|
@@ -232,7 +232,7 @@ is met.
|
|
|
"min_age": "0ms",
|
|
|
"actions": {
|
|
|
"rollover": {
|
|
|
- "max_size": "50gb",
|
|
|
+ "max_primary_shard_size": "50gb",
|
|
|
"max_age": "30d"
|
|
|
}
|
|
|
}
|