-
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
🐛 bugSomething isn't workingSomething isn't working
Description
What
When lots of big messages are sent to Redis it can't cope. The following is logged in the console:
# WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
See https://stackoverflow.com/questions/76830848/redis-warning-memory-overcommit-must-be-enabled for discussions on enabling the overcommit support.
Steps to reproduce the behavior:
Got the behaviour when testing sending the full product details to Redis when migrating historic events.
Expected behavior
Redis should keep running
Metadata
Metadata
Assignees
Labels
🐛 bugSomething isn't workingSomething isn't working