You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 16, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: docs/im/ism/policies.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Field | Description | Type | Required | Read Only
41
41
42
42
---
43
43
44
-
## States
44
+
## States
45
45
46
46
A state is the description of the status that the managed index is currently in. A managed index can be in only one state at a time. Each state has associated actions that are executed sequentially on entering a state and transitions that are checked after all the actions have been completed.
47
47
@@ -205,7 +205,7 @@ Set `index.opendistro.index_state_management.rollover_alias` as the alias to rol
205
205
206
206
Parameter | Description | Type | Example | Required
207
207
:--- | :--- |:--- |:--- |
208
-
`min_size` | The minimum size of the total primary shard storage (not counting replicas) required to roll over the index. For example, if you set `min_size` to 100 GiB and your index has 5 primary shards and 5 replica shards of 20 GiB each, the total size of the primaries is 100 GiB, so the rollover occurs. ISM doesn't check indices continually, so it doesn't roll over indices at exactly 100 GiB. Instead, if an index is continuously growing, ISM might check it at 99 GiB, not perform the rollover, check again when the shards reach 105 GiB, and then perform the operation. | `string` | `20gb` or `5mb` | No
208
+
`min_size` | The minimum size of the total primary shard storage (not counting replicas) required to roll over the index. For example, if you set `min_size` to 100 GiB and your index has 5 primary shards and 5 replica shards of 20 GiB each, the total size of all primary shards is 100 GiB, so the rollover occurs. ISM doesn't check indices continually, so it doesn't roll over indices at exactly 100 GiB. Instead, if an index is continuously growing, ISM might check it at 99 GiB, not perform the rollover, check again when the shards reach 105 GiB, and then perform the operation. | `string` | `20gb` or `5mb` | No
209
209
`min_doc_count` | The minimum number of documents required to roll over the index. | `number` | `2000000` | No
210
210
`min_index_age` | The minimum age required to roll over the index. Index age is the time between its creation and the present. | `string` | `5d` or `7h` | No
`min_index_age` | The minimum age of the index required to transition. | `string` | No
396
396
`min_doc_count` | The minimum document count of the index required to transition. | `number` | No
397
-
`min_size` | The minimum size of the index required to transition. | `string` | No
397
+
`min_size` | The minimum size of the total primary shard storage (not counting replicas). For example, if you set `min_size` to 100 GiB and your index has 5 primary shards and 5 replica shards of 20 GiB each, the total size of all primary shards is 100 GiB, so your index is transitioned to the next state. | `string` | No
398
398
`cron` | The `cron` job that triggers the transition if no other transition happens first. | `object` | No
399
399
`cron.cron.expression` | The `cron` expression that triggers the transition. | `string` | Yes
400
400
`cron.cron.timezone` | The timezone that triggers the transition. | `string` | Yes
@@ -661,6 +661,6 @@ After 30 days, the policy moves this index into a `delete` state. The service se
661
661
}
662
662
```
663
663
664
-
This diagram shows the `states`, `transitions`, and `actions` of the above policy as a finite-state machine. For more information about finite-state machines, see [Wikipedia](https://en.wikipedia.org/wiki/Finite-state_machine).
664
+
This diagram shows the `states`, `transitions`, and `actions` of the above policy as a finite-state machine. For more information about finite-state machines, see [Wikipedia](https://en.wikipedia.org/wiki/Finite-state_machine).
0 commit comments