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.

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
Changes from 4 commits
Commits
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
13 changes: 7 additions & 6 deletions docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,14 @@
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>>. In the
Copy link
Contributor

@andreidan andreidan Jun 30, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we expand this a bit and say something like:

The `searchable_snapshot` action requires a system that uses <<data-tiers,data tiers>> 
as it will mount the index directly on the corresponding tier using the
 <<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>> setting.

Maybe @jrodewig has a better suggestion here? (I don't particularly like "a system that uses ..." but not sure how else to phrase this).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @andreidan. I pushed some changes to incorporate the index.routing.allocation.include._tier_preference setting content.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks James

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