From 2f09b08d5c9fab002f1b9d3d51e733cf93bd4f31 Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Fri, 7 Dec 2018 17:29:27 +0100 Subject: [PATCH 1/5] Explicitly recommend to forceMerge before freezing given the benchmark results on #34352 it's important to recommend users to `_force_merge` their indice to a single segment before freezing. --- docs/reference/frozen-indices.asciidoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc index 28264547575b7..26f59e02381ad 100644 --- a/docs/reference/frozen-indices.asciidoc +++ b/docs/reference/frozen-indices.asciidoc @@ -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 <>. +It's highly recommended to <> you indices prior to freezing them to ensure the indices only have a single +segment on disk. This will provide much better compression but also prevents the need for additional data-structures required for +aggregation to be build on every request. + +[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 From 03f5a28983208d38f4581df9031cde829e7dced6 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Fri, 7 Dec 2018 18:12:53 +0100 Subject: [PATCH 2/5] Update docs/reference/frozen-indices.asciidoc Co-Authored-By: s1monw --- docs/reference/frozen-indices.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc index 26f59e02381ad..3d80dbedd44f8 100644 --- a/docs/reference/frozen-indices.asciidoc +++ b/docs/reference/frozen-indices.asciidoc @@ -29,7 +29,7 @@ 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 <>. -It's highly recommended to <> you indices prior to freezing them to ensure the indices only have a single +It's highly recommended to <> your indices prior to freezing to ensure that each shard has only a single segment on disk. This will provide much better compression but also prevents the need for additional data-structures required for aggregation to be build on every request. From bab6182790526a676955f5599d31b5d08ca1cfc5 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Fri, 7 Dec 2018 18:12:59 +0100 Subject: [PATCH 3/5] Update docs/reference/frozen-indices.asciidoc Co-Authored-By: s1monw --- docs/reference/frozen-indices.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc index 3d80dbedd44f8..e86f94d32b296 100644 --- a/docs/reference/frozen-indices.asciidoc +++ b/docs/reference/frozen-indices.asciidoc @@ -30,7 +30,7 @@ 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 <>. It's highly recommended to <> your indices prior to freezing to ensure that each shard has only a single -segment on disk. This will provide much better compression but also prevents the need for additional data-structures required for +segment on disk. This will not only provide much better compression but also simplify the data structures needed to service aggregation requests. aggregation to be build on every request. [source,js] From b0f2c9c32e543f27bac5c9b71c863929050cbe00 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Fri, 7 Dec 2018 18:15:29 +0100 Subject: [PATCH 4/5] Update docs/reference/frozen-indices.asciidoc Co-Authored-By: s1monw --- docs/reference/frozen-indices.asciidoc | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc index e86f94d32b296..fd50b4a68c9d6 100644 --- a/docs/reference/frozen-indices.asciidoc +++ b/docs/reference/frozen-indices.asciidoc @@ -31,7 +31,6 @@ Since indices that are eligible for freezing are unlikely to change in the futur It's highly recommended to <> your indices prior to freezing to ensure that each shard has only a single segment on disk. This will not only provide much better compression but also simplify the data structures needed to service aggregation requests. -aggregation to be build on every request. [source,js] -------------------------------------------------- From 290c0c78fd007897871c0ce44ff0cad5e2f8ff0c Mon Sep 17 00:00:00 2001 From: Simon Willnauer Date: Fri, 7 Dec 2018 18:16:56 +0100 Subject: [PATCH 5/5] removing the future tense --- docs/reference/frozen-indices.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc index fd50b4a68c9d6..4002df887665d 100644 --- a/docs/reference/frozen-indices.asciidoc +++ b/docs/reference/frozen-indices.asciidoc @@ -30,7 +30,8 @@ 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 <>. It's highly recommended to <> your indices prior to freezing to ensure that each shard has only a single -segment on disk. This will not only provide much better compression but also simplify the data structures needed to service aggregation requests. +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] --------------------------------------------------