Sign in

Exit code 137 out of nowhere. Who killed my Node.js API?

Solveddockerkubernetesmemory1 replies · 243 views · started
Reply
Accepted solution by Silas W. — hmmm confirm it's really an OOM kill: kubectl describe pod shows Last State: Terminated, Reason: OOMKilled, or for Docker run docker…
  1. Silas Weber
    @silas.weber

    ok weird one migrated the Node.js API from a VM to containres. On the VM it was fine for years. In a container with 768Mi:

    kliled with 137 within an hour of heavy traffic. same code, same traffic... what changed?

    on the VM, nothing ever complained. i suspect teh runtime is behaving differently inside teh container, but idk what to check. any advice on siizng a 768Mi container properly would be much appreciated.

    4
  2. Silas W.
    @silas.weber88
    Accepted solution

    hmmm confirm it's really an OOM kill: kubectl describe pod shows Last State: Terminated, Reason: OOMKilled, or for Docker run docker inspect <container> and look for "OOMKilled": true. On the node, dmesg or journalctl -k shows Memory cgroup out of memory: Killed process.

    3 5 helpful

Reply to this topic

Sign in or create an account to reply.