From 4564085528912a7caa4dcbbbf2bb9bfc06acb808 Mon Sep 17 00:00:00 2001 From: Frederik Bosch Date: Tue, 23 Oct 2018 12:25:04 +0200 Subject: [PATCH] [DOCS] Force Merge: clarify execution and storage requirements (#33882) --- docs/reference/indices/forcemerge.asciidoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc index 57fe746d59bb2..a28d5eaa8586c 100644 --- a/docs/reference/indices/forcemerge.asciidoc +++ b/docs/reference/indices/forcemerge.asciidoc @@ -55,7 +55,11 @@ POST /kimchy/_forcemerge?only_expunge_deletes=false&max_num_segments=100&flush=t === Multi Index The force merge API can be applied to more than one index with a single call, or -even on `_all` the indices. +even on `_all` the indices. Multi index operations are executed one shard at a +time per node. Force merge makes the storage for the shard being merged +temporarily increase, up to double its size in case `max_num_segments` is set +to `1`, as all segments need to be rewritten into a new one. + [source,js] --------------------------------------------------