Best Products
Launches
Launch archive
Most-loved launches by the community
Launch Guide
Checklists and pro tips for launching
News
Newsletter
The best of Product Hunt, every day
Stories
Tech news, interviews, and tips from makers
Changelog
New Product Hunt features and releases
Forums
Forums
Ask questions, find support, and connect
Kitty Points Leaderboard
The highest scoring community members
Streaks
The most active community members
Events
Meet others online and in-person
Advertise
Subscribe
Sign in
Clear text
recent
p/basedash
by
Max Musing
•
2mo ago
What was killing our healthy Kubernetes pods
... graceful shutdown writes a log line. Both would be in BetterStack, and there was nothing. So whatever killed the pod didn t let it run any more JavaScript on the way out. The convenient theory The convenient theory was
OOM
. Node.js services hit the cgroup limit, the kernel reaps the process with SIGKILL, the dashboards spike, the pod restarts. We ve seen it before, and it s the first thing anyone reaches for. We looked, and container memory stayed comfortably ... ... hadn t fired on any of the dead pods, the heap was healthy, and native memory looked normal. It was a tidy theory, and it was wrong. The exit code that didn t match the story When
OOM
1
6
Subscribe
Sign in