From 9daaae27b3677fee96f09093a9480fd1148f8ba4 Mon Sep 17 00:00:00 2001 From: mikemccand Date: Wed, 7 May 2014 13:49:46 -0400 Subject: [PATCH] clarify that CMS defaults change is coming in 1.2 --- docs/reference/index-modules/merge.asciidoc | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/reference/index-modules/merge.asciidoc b/docs/reference/index-modules/merge.asciidoc index d0ec9549173..98b42c52fa3 100644 --- a/docs/reference/index-modules/merge.asciidoc +++ b/docs/reference/index-modules/merge.asciidoc @@ -201,9 +201,14 @@ The scheduler supports the following settings: `index.merge.scheduler.max_thread_count`:: -The maximum number of concurrent merge threads that may run at once. Defaults -to `1` which works best with spinning-magnets disks. If you are using -a good solid-state disk (SSD) instead then try setting this to `3`. +The maximum number of threads to perform the merge operation. Defaults to +`Math.max(1, Math.min(3, Runtime.getRuntime().availableProcessors() / 2))`. + +coming[1.2.0] + +The default will change to `1` which works best with spinning-magnets +disks. If you are using a good solid-state disk (SSD) instead then try +setting this to `3`. [float] ==== SerialMergeScheduler