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
This commit is contained in:
parent
7945848dd6
commit
e542c03bea
|
@ -2,7 +2,7 @@
|
||||||
=== Number of threads
|
=== Number of threads
|
||||||
|
|
||||||
Elasticsearch uses a number of thread pools for different types of operations.
|
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
|
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
|
sure that the number of threads that the Elasticsearch user can create is at
|
||||||
least 4096.
|
least 4096.
|
||||||
|
|
||||||
|
@ -10,3 +10,6 @@ This can be done by setting <<ulimit,`ulimit -u 4096`>> as root before
|
||||||
starting Elasticsearch, or by setting `nproc` to `4096` in
|
starting Elasticsearch, or by setting `nproc` to `4096` in
|
||||||
<<limits.conf,`/etc/security/limits.conf`>>.
|
<<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.
|
||||||
|
|
Loading…
Reference in New Issue