|
5 | 5 | Phases allowed: hot, cold, frozen.
|
6 | 6 |
|
7 | 7 | Takes a snapshot of the managed index in the configured repository and mounts it
|
8 |
| -as a <<searchable-snapshots,{search-snap}>>. |
9 |
| - |
10 |
| -In the frozen phase, the action mounts a <<partially-mounted,partially mounted |
11 |
| -index>>. In other phases, the action mounts a <<fully-mounted,fully mounted |
12 |
| -index>>. If the original index is part of a |
| 8 | +as a <<searchable-snapshots,{search-snap}>>. If the index is part of a |
13 | 9 | <<data-streams, data stream>>, the mounted index replaces the original index in
|
14 |
| -the data stream. |
| 10 | +the stream. |
| 11 | + |
| 12 | +The `searchable_snapshot` action requires <<data-tiers,data tiers>>. The action |
| 13 | +uses the |
| 14 | +<<tier-preference-allocation-filter,`index.routing.allocation.include._tier_preference`>> |
| 15 | +setting to mount the index directly to the phase's corresponding data tier. In |
| 16 | +the frozen phase, the action mounts a <<partially-mounted,partially mounted |
| 17 | +index>> to the frozen tier. In other phases, the action mounts a |
| 18 | +<<fully-mounted,fully mounted index>> to the corresponding data tier. |
15 | 19 |
|
16 | 20 | IMPORTANT: If the `searchable_snapshot` action is used in the hot phase the
|
17 | 21 | subsequent phases cannot include the `shrink`, `forcemerge`, or `freeze`
|
|
0 commit comments