War Story: How a Kubernetes 1.32 Node OOM Kill Cascaded Into a 2-Hour Outage for Our Video Streaming Service
At 19:42 UTC on March 14, 2024, our video streaming service serving 4.2 million concurrent viewers lost 92% of traffic in 11 minutes, triggered by a single Kubernetes 1.32 node OOM kill that cascaded across 18 availability zones. ⭐ kubernetes/kubernetes — 122,018 stars, 42,991 forks Data pulled li
ORIGINAL SOURCE →via Dev.to
ADVERTISEMENT
⚡ STAY AHEAD
Events like this, convergence-verified across 689 sources, land in your inbox every Sunday. Free.
GET THE SUNDAY BRIEFING →RELATED · conflict
- [CONFLICT] Intermodal Asia
- [CONFLICT] Securing the Untrusted Agentic Development Layer
- [CONFLICT] After a Maryland teacher’s death, a 200-piece Judaica collection finds new life in a Jewish museum
- [CONFLICT] 'A little too far': McAvoy tossed for violent slas...
- [CONFLICT] What to watch in Israel: 'Fauda' season 5, 'Unconditional' lead wave of new releases
- [CONFLICT] Resultado La Caribeña noche hoy <p>1</p> de <p>mayo</p>