Hi All.
We Have a Debian 10 installation with 8GiB of RAM. Memory Hot-plugging is enabled as explained in wiki (Both udev rules and kernel parameter are set). The Server is Used as an Ingress in Kubernetes cluster and uses nginx. Under High Load, we discovered nginx is failing to fork new threads for new connections due to reaching max allowed threads (Our Post regarding the threads-max). Digging deeper, we found that while booting the kernel is discovering only 1GiB of Memory and therefor setting a very Low amount of max allowed threads (7055):
However the Memory is recognized completely by VM when booted and Hot-Plugging is working seamlessly.
Disabling the Memory Hotplug Solves the problem all together:
Any Help is super Welcomed
We Have a Debian 10 installation with 8GiB of RAM. Memory Hot-plugging is enabled as explained in wiki (Both udev rules and kernel parameter are set). The Server is Used as an Ingress in Kubernetes cluster and uses nginx. Under High Load, we discovered nginx is failing to fork new threads for new connections due to reaching max allowed threads (Our Post regarding the threads-max). Digging deeper, we found that while booting the kernel is discovering only 1GiB of Memory and therefor setting a very Low amount of max allowed threads (7055):
Bash:
root@deb:~>>> dmesg | grep Memory:
[ 0.282335] Memory: 903820K/1048032K available (10252K kernel code, 1242K rwdata, 3328K rodata, 1600K init, 2260K bss, 144212K reserved, 0K cma-reserved)
root@deb:~>>> cat /proc/sys/kernel/threads-max
7055However the Memory is recognized completely by VM when booted and Hot-Plugging is working seamlessly.
Disabling the Memory Hotplug Solves the problem all together:
Bash:
root@deb:~>>> dmesg | grep Memory:
[ 1.156223] Memory: 8129300K/8388064K available (10252K kernel code, 1242K rwdata, 3328K rodata, 1600K init, 2260K bss, 258764K reserved, 0K cma-reserved)
root@deb:~>>> cat /proc/sys/kernel/threads-max
63510Any Help is super Welcomed
Last edited: