Redis - OOM error thrown even when memory is not the issue

I recently tried setting logs.server.level to "info" for my Redis deployment:

log:
  # Supported values ["stdout", "stream"]
  outputs: ["stdout"]
  node:
    level: "info"
    bufferedLines: 2000
  server:
    level: "info"
  metricsExporter:
    bufferedLines: 2000

This, in turn, caused a CrashLoopBackoff. It can be seen the exit code thrown is 137, which indicates OOM.

Upon further investigation, it can be seen that Redis doesn't seem to support info: https://www.papertrail.com/help/redis/

My question is, why would this then throw a 137 error code, indicating OOM, for my Kubernetes deployment?

Redis - OOM error thrown even when memory is not the issue

0 Answers