Discourse docker redis warning messages

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…

요즘에는 discourse-setup가 이러한 문제를 처리하도록 설계되었습니다.

@pfaffman … 더 이상 문제가 아닌지 모르겠습니다.

discourse-setup는 THP, maxconn, overcommit_memory 관련 설정을 처리하지 않습니다. RAM이 2GB 이하인 경우 스왑을 추가하는 것만 수행합니다. 저는 제 환경에서 해당 항목들을 설정해 두었지만, 이 메시지가 실제로 사라지는지 꼼꼼히 확인해 보지는 않았습니다. 해당 메시지가 스크롤되어 지나가는 것처럼 보이거든요?

호스트에서 발생하는 것으로 추정되지만, 이로 인해 의문이 생깁니다.