help!! migrated the Go microservice from a VM to containers. On the VM it was fine for years. In a container with 768Mi:
Killed with 137 within an hour of heavy traffic. Same code, same traffic. What changed?
on the VM, nothing ever complained... i suspect the runtime is behaving differently inside the container, but idk what to check, any advice on sizing a 768Mi container properly would be much appreciated.
sorry forgot to say confirmed: Reason: OOMKilled and dmesg shows teh cgroup OOM line for our process.
lol same thing happened to me confirm its realy 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. hope that helps :)
Sign in or create an account to reply.
