Valkey Over RDMA valkey-server rdma-test log:
---------------
16480:M 31 Aug 2026 20:58:57.175 # 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.
16480:M 31 Aug 2026 20:58:57.175 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
16480:M 31 Aug 2026 20:58:57.175 * Valkey version=255.255.255, bits=64, commit=7448f1fc, modified=0, pid=16480, just started
16480:M 31 Aug 2026 20:58:57.175 * Configuration loaded
16480:M 31 Aug 2026 20:58:57.175 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16480:M 31 Aug 2026 20:58:57.206 * monotonic clock: X86 TSC @ 2300.45 ticks/us
16480:M 31 Aug 2026 20:58:57.206 * Running mode=standalone, port=0.
16480:M 31 Aug 2026 20:58:57.295 * Static Module 'lua' successfully loaded
16480:M 31 Aug 2026 20:58:57.295 * Server initialized
16480:M 31 Aug 2026 20:58:57.295 * Ready to accept connections rdma
16480:M 31 Aug 2026 20:58:58.187 # RDMA Accepting client connection: RDMA: accept failed
16480:M 31 Aug 2026 20:58:58.192 # RDMA Accepting client connection: RDMA: accept failed
16480:M 31 Aug 2026 20:58:58.196 # RDMA Accepting client connection: RDMA: accept failed
16480:M 31 Aug 2026 20:58:58.201 # RDMA Accepting client connection: RDMA: accept failed
We've seen some RDMA failures recently like:
https://github.com/valkey-io/valkey/actions/runs/33438572088/job/99641089735?pr=4577