nerd
nerd copied to clipboard
Slow OOM containers are complete gracefully without any hint
When running the ethereum client nerd job run ethereum/client-go as a job the process will (seemingly) gracefully end. What happened is that the process slowly reached the memory constrained and Kubernetes asked the process gracefully to exit. running it like this solves the problem: nerd job run --memory=6GiB ethereum/client-go
We should probably catch this for the CLI user by reading out OOM events and displaying them inline:
JOB IMAGE INPUT OUTPUT MEMORY VCPU CREATED AT PHASE DETAILS
flights2-co2-calc nerdalize/co2-calculator flights2 1.1 1.0 27 minutes ago Completed OOM detected