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
•
27d ago
What was killing our healthy Kubernetes pods
... looked, and container memory stayed comfortably below the limit on every restart we examined. The in-app memory watchdog (which logs and shuts down at 80% RSS) 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 stopped fitting, we walked back to kubectl and looked at what it actually said about ... ... 3584MB container. Worker went from 3072MB to 2456MB on a 4096MB container. 2 reasons: --max-old-space-size only bounds V8 s old generation. It doesn t bound native memory used by Buffers, ICU data, worker-thread
heaps
1
12
Subscribe
Sign in