The pod.txt shows that redis-enterprise-node container was restarted with reason OOMKilled and Exit Code 137

Last updated 22, Mar 2024

Symptoms:

The Redis Enterprise Cluster initiated shard failover. The file pod.txt reports the error as follows

  services-rigger:
    ...
    State:          Running
      Started:      Sun, 22 Jan 2023 19:39:07 +0200
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Fri, 20 Jan 2023 15:16:46 +0200
      Finished:     Sun, 22 Jan 2023 19:33:58 +0200
    Ready:          True
    Restart Count:  1
    ...

Changes:

Non-Redis containers may consume more RAM than expected. The Redis Enterprise containers have RAM and CPU limits.

Cause:

Pods running on the worker can consume the worker's ram.

Solution:

Consult your k8 admin

References:

Resource Management for Pods and Containers