OpenSearch/docs/reference/setup/sysconfig/threads.asciidoc

[[max-number-of-threads]]
=== Number of threads

Elasticsearch uses a number of thread pools for different types of operations.
It is important that it is able to create new threads whenever needed. Make
sure that the number of threads that the Elasticsearch user can create is at
least 4096.

This can be done by setting <<ulimit,`ulimit -u 4096`>> as root before
starting Elasticsearch, or by setting `nproc` to `4096` in
<<limits.conf,`/etc/security/limits.conf`>>.

The package distributions when run as services under `systemd` will configure
the number of threads for the Elasticsearch process automatically. No
additional configuration is required.
Docs: Complete rewrite of setup, installation, and configuration docs 2016-04-03 10:09:24 -04:00			`[[max-number-of-threads]]`
			`=== Number of threads`

			`Elasticsearch uses a number of thread pools for different types of operations.`
Clarify that number of threads is set by packages This commit clarifies that on systemd the packages already set the number of threads for the Elasticsearch process. Relates #27840 2017-12-15 11:29:13 -05:00			`It is important that it is able to create new threads whenever needed. Make`
Docs: Complete rewrite of setup, installation, and configuration docs 2016-04-03 10:09:24 -04:00			`sure that the number of threads that the Elasticsearch user can create is at`
Fix max number of threads bootstrap docs Previously the bootstrap check for max number of threads was increased from 2048 to 4096 yet the docs were never adjusted for this change. This commit addresses this so the docs are in-line with the limit enforced in the bootstrap check. Relates #27511 2017-11-28 22:17:22 -05:00			`least 4096.`
Docs: Complete rewrite of setup, installation, and configuration docs 2016-04-03 10:09:24 -04:00
Fix max number of threads bootstrap docs Previously the bootstrap check for max number of threads was increased from 2048 to 4096 yet the docs were never adjusted for this change. This commit addresses this so the docs are in-line with the limit enforced in the bootstrap check. Relates #27511 2017-11-28 22:17:22 -05:00			This can be done by setting <<ulimit,`ulimit -u 4096`>> as root before
			starting Elasticsearch, or by setting `nproc` to `4096` in
Docs: Complete rewrite of setup, installation, and configuration docs 2016-04-03 10:09:24 -04:00			<<limits.conf,`/etc/security/limits.conf`>>.

Clarify that number of threads is set by packages This commit clarifies that on systemd the packages already set the number of threads for the Elasticsearch process. Relates #27840 2017-12-15 11:29:13 -05:00			The package distributions when run as services under `systemd` will configure
			`the number of threads for the Elasticsearch process automatically. No`
			`additional configuration is required.`