From d290284e3b243d71ba215307047a6e232c75b320 Mon Sep 17 00:00:00 2001 From: Frederik Bosch Date: Thu, 20 Sep 2018 08:20:23 +0200 Subject: [PATCH 1/3] Multi index operations are executed synchronously. Because of the additional space required you I was wondering how the operations are executed: sync or async. Docs did not give me an answer. Using trial and error I found out it is executed synchronously. I thought the information to be useful for others too. --- docs/reference/indices/forcemerge.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc index 57fe746d59bb2..b1fdb8241b9fb 100644 --- a/docs/reference/indices/forcemerge.asciidoc +++ b/docs/reference/indices/forcemerge.asciidoc @@ -55,7 +55,8 @@ 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 synchronously (one +index at a time). [source,js] -------------------------------------------------- From 026365d9ba7c31e616c8901ec8b768fb4d7f6913 Mon Sep 17 00:00:00 2001 From: Frederik Bosch Date: Fri, 5 Oct 2018 17:38:34 +0200 Subject: [PATCH 2/3] Update remark on sync/async merging multiple indices --- docs/reference/indices/forcemerge.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc index b1fdb8241b9fb..62011c768e9f2 100644 --- a/docs/reference/indices/forcemerge.asciidoc +++ b/docs/reference/indices/forcemerge.asciidoc @@ -55,8 +55,8 @@ 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. Multi index operations are executed synchronously (one -index at a time). +even on `_all` the indices. Multi index operations are executed async for all nodes, +but one shard at a time per node. This will cause storage to increase per node. [source,js] -------------------------------------------------- From aaec237b73f8a6124379ff5e2417c941fc90230e Mon Sep 17 00:00:00 2001 From: javanna Date: Tue, 23 Oct 2018 12:21:28 +0200 Subject: [PATCH 3/3] clarified sentence --- docs/reference/indices/forcemerge.asciidoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc index 62011c768e9f2..a28d5eaa8586c 100644 --- a/docs/reference/indices/forcemerge.asciidoc +++ b/docs/reference/indices/forcemerge.asciidoc @@ -55,8 +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. Multi index operations are executed async for all nodes, -but one shard at a time per node. This will cause storage to increase per node. +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] --------------------------------------------------