From 7f857b62f4d91b468dd32c0eba86a6e29cca4458 Mon Sep 17 00:00:00 2001 From: Frederic Dartayre <30438455+fdartayre@users.noreply.github.com> Date: Wed, 26 Oct 2022 20:04:39 +0200 Subject: [PATCH] Update threadpool.asciidoc (#90098) * Update threadpool.asciidoc Starting from 8.0 the value of the `node.processors` setting is bounded by the number of available processors https://github.com/elastic/elasticsearch/pull/44894 * Update docs/reference/modules/threadpool.asciidoc Co-authored-by: Adam Locke (cherry picked from commit fe0036fdbfcb5e44e349123bb5caed78ff076bd2) # Conflicts: # docs/reference/modules/threadpool.asciidoc --- docs/reference/modules/threadpool.asciidoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/reference/modules/threadpool.asciidoc b/docs/reference/modules/threadpool.asciidoc index e0b99ddf15630..25423dc589b3a 100644 --- a/docs/reference/modules/threadpool.asciidoc +++ b/docs/reference/modules/threadpool.asciidoc @@ -177,7 +177,10 @@ thread_pool: The number of processors is automatically detected, and the thread pool settings are automatically set based on it. In some cases it can be useful to override the number of detected processors. This can be done by explicitly setting the -`node.processors` setting. +`node.processors` setting. This setting is bounded by the number of available +processors and accepts floating point numbers, which can be useful in environments +where the {es} nodes are configured to run with CPU limits, such as cpu +shares or quota under `Cgroups`. [source,yaml] --------------------------------------------------