From f0683e1a4b0474d4352e761dacd09b277acf4dd1 Mon Sep 17 00:00:00 2001 From: Glen Smith Date: Thu, 21 Jul 2022 09:27:37 -0600 Subject: [PATCH] Clarify same indices requests are blocked (#80228) Make it clear that requests to force merge _the same indices_ will be blocked. (Used the same language from current release, v7.15.) --- docs/reference/indices/forcemerge.asciidoc | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc index a28d5eaa8586c..9a947dde175a4 100644 --- a/docs/reference/indices/forcemerge.asciidoc +++ b/docs/reference/indices/forcemerge.asciidoc @@ -6,9 +6,13 @@ API. The merge relates to the number of segments a Lucene index holds within each shard. The force merge operation allows to reduce the number of segments by merging them. -This call will block until the merge is complete. If the http connection is -lost, the request will continue in the background, and any new requests will -block until the previous force merge is complete. +=== Blocks during a force merge + +Calls to this API block until the merge is complete. If the client +connection is lost before completion then the force merge process +will continue in the background. Any new requests to force merge the +same indices will also block until the ongoing force merge is +complete. WARNING: Force merge should only be called against *read-only indices*. Running force merge against a read-write index can cause very large segments to be produced