Skip to content

Explicitly recommend to forceMerge before freezing #36376

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 5 commits into from
Dec 7, 2018
Merged

Explicitly recommend to forceMerge before freezing #36376

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2f09b08
Explicitly recommend to forceMerge before freezing
s1monw Dec 7, 2018
03f5a28
Update docs/reference/frozen-indices.asciidoc
clintongormley Dec 7, 2018
bab6182
Update docs/reference/frozen-indices.asciidoc
clintongormley Dec 7, 2018
b0f2c9c
Update docs/reference/frozen-indices.asciidoc
clintongormley Dec 7, 2018
290c0c7
removing the future tense
s1monw Dec 7, 2018
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
11 changes: 11 additions & 0 deletions docs/reference/frozen-indices.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,17 @@ data structures on demand which can cause page faults and garbage collections, w

Since indices that are eligible for freezing are unlikely to change in the future, disk space can be optimized as described in <<tune-for-disk-usage>>.

It's highly recommended to <<indices-forcemerge,`_forcemerge`>> your indices prior to freezing to ensure that each shard has only a single
segment on disk. This not only provides much better compression but also simplifies the data structures needed to service aggregation
or sorted search requests.

[source,js]
--------------------------------------------------
POST /twitter/_forcemerge?max_num_segments=1
--------------------------------------------------
// CONSOLE
// TEST[setup:twitter]

== Searching a frozen index

Frozen indices are throttled in order to limit memory consumptions per node. The number of concurrently loaded frozen indices per node is
Expand Down