From: Ben England Date: Sun, 5 May 2019 22:38:50 +0000 (-0400) Subject: doc: remove recommendation for kernel.pid_max X-Git-Tag: v15.1.0~2253^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c23369975d11cc3b792f42dd55193097f90a2173;p=ceph.git doc: remove recommendation for kernel.pid_max now that Ceph uses async messenger, setting kernel.pid_max = 4194303 should not be necessary anymore. Even if kernel thread limit is 32K and we have 100 drives, that's 320 threads per OSD, I think that should be enough. Signed-off-by: Ben England --- diff --git a/doc/start/hardware-recommendations.rst b/doc/start/hardware-recommendations.rst index 30e00a892461..a3277b90f132 100644 --- a/doc/start/hardware-recommendations.rst +++ b/doc/start/hardware-recommendations.rst @@ -205,16 +205,6 @@ is up to date. See `OS Recommendations`_ for notes on ``glibc`` and ``syncfs(2)`` to ensure that your hardware performs as expected when running multiple OSDs per host. -Hosts with high numbers of OSDs (e.g., > 20) may spawn a lot of threads, -especially during recovery and rebalancing. Many Linux kernels default to -a relatively small maximum number of threads (e.g., 32k). If you encounter -problems starting up OSDs on hosts with a high number of OSDs, consider -setting ``kernel.pid_max`` to a higher number of threads. The theoretical -maximum is 4,194,303 threads. For example, you could add the following to -the ``/etc/sysctl.conf`` file:: - - kernel.pid_max = 4194303 - Networks ========