Skip to content

Commit 183c32d

Browse files
frederikboschjavanna
authored andcommitted
[DOCS] Force Merge: clarify execution and storage requirements (#33882)
1 parent 4bda9bd commit 183c32d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/reference/indices/forcemerge.asciidoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,11 @@ POST /kimchy/_forcemerge?only_expunge_deletes=false&max_num_segments=100&flush=t
5555
=== Multi Index
5656

5757
The force merge API can be applied to more than one index with a single call, or
58-
even on `_all` the indices.
58+
even on `_all` the indices. Multi index operations are executed one shard at a
59+
time per node. Force merge makes the storage for the shard being merged
60+
temporarily increase, up to double its size in case `max_num_segments` is set
61+
to `1`, as all segments need to be rewritten into a new one.
62+
5963

6064
[source,js]
6165
--------------------------------------------------

0 commit comments

Comments
 (0)