Mensagens de aviso do Docker Discourse com Redis

188:M 13 Sep 04:27:11.292 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

My question is, is this on the host or the docker? Because on the host it’s already 1024. I checked with cat /proc/sys/net/core/somaxconn

WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

My server is a multi-service service and I run many services on it, including other databases (mariadb) for instance. What are the consequences of disabling this on other services and databases?

WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

This one I fixed with the command on the host fine. But I feel like there should be more documentation on this warnings, and how they affect our systems. sorry if my questions are dumb…

O discourse-setup foi criado para lidar com problemas como este atualmente.

Não tenho certeza se isso ainda é um problema, @pfaffman

discourse-setup não configura THP, maxconn ou overcommit_memory; ele apenas adiciona swap se a RAM for ≤2GB. Eu configurei essas opções nas minhas instalações, mas ainda não analisei cuidadosamente se elas realmente fazem essa mensagem desaparecer. Parece que vejo essas mensagens passando rapidamente?

Presumo que seja no host, mas isso me deixa em dúvida.