Skip to content

Data Tier correlation for searchable_snapshot mount location #74706

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jun 30, 2021
Merged

Data Tier correlation for searchable_snapshot mount location #74706

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
b0b4aa9
+dataTier corr. for searchable_snapshot mounts
stefnestor Jun 29, 2021
d3f6248
Add requirement sentence. Minor reorg.
jrodewig Jun 29, 2021
4cf98d9
Forgot to commit
jrodewig Jun 29, 2021
5beebfb
Minor reword
jrodewig Jun 29, 2021
a568ea9
Address feedback
jrodewig Jun 30, 2021
b614ed6
Address feedback
jrodewig Jun 30, 2021
09086bc
reword
jrodewig Jun 30, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,17 @@
Phases allowed: hot, cold, frozen.

Takes a snapshot of the managed index in the configured repository and mounts it
as a <<searchable-snapshots,{search-snap}>>.

In the frozen phase, the action mounts a <<partially-mounted,partially mounted
index>>. In other phases, the action mounts a <<fully-mounted,fully mounted
index>>. If the original index is part of a
as a <<searchable-snapshots,{search-snap}>>. If the index is part of a
<<data-streams, data stream>>, the mounted index replaces the original index in
the data stream.
the stream.

The `searchable_snapshot` action requires <<data-tiers,data tiers>>. The action
uses the
<<tier-preference-allocation-filter,`index.routing.allocation.include._tier_preference`>>
setting to mount the index directly to the phase's corresponding data tier. In
the frozen phase, the action mounts a <<partially-mounted,partially mounted
index>> to the frozen tier. In other phases, the action mounts a
<<fully-mounted,fully mounted index>> to the corresponding data tier.

IMPORTANT: If the `searchable_snapshot` action is used in the hot phase the
subsequent phases cannot include the `shrink`, `forcemerge`, or `freeze`
Expand Down