Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to overcome warnings in redis container log. #165

Closed
MattCzerner opened this issue Sep 24, 2018 · 2 comments
Closed

How to overcome warnings in redis container log. #165

MattCzerner opened this issue Sep 24, 2018 · 2 comments
Labels
question Usability question, not directly related to an error with the image

Comments

@MattCzerner
Copy link

Redis outputs many warnings in default state.

These warnings are referencing to bad configuration of image:

shopsys-framework-redis               | 1:M 24 Sep 10:00:56.234 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
shopsys-framework-redis               | 1:M 24 Sep 10:00:56.234 # 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.
shopsys-framework-redis               | 1:M 24 Sep 10:00:56.235 # 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.

These logs even say how to solve them so I wonder why it is not configured properly in dockerfile and if there is a reason for it, how can I configure it myself.

Would be nice if this could be defined as env variables.

@itamarhaber
Copy link
Member

Hello @MattCzerner

There are previous (closed) issues about these, e.g. #14, #19, #20, #55. TL;DR these need to be set at the host OS level.

@gaieges
Copy link

gaieges commented Apr 30, 2019

@MattCzerner are you aware if there's a way to reduce these log messages to info vs warning?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Usability question, not directly related to an error with the image
Projects
None yet
Development

No branches or pull requests

4 participants