From Production Downtime Due to a Network Error to a Commit in Upstream Linkerd
summary
Talk describes diagnosing a production downtime caused by a network bug in a service mesh and the process of fixing it by contributing a patch upstream to Linkerd. It covers the incident investigation steps, reproducing the network error, and the code changes and workflow used to get the fix accepted into Linkerd’s upstream repository.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:59Incident cause and analysis
- 9:14Reproducing the issue
- 13:09TCP User Timeout solution
- 15:37Linkerd integration
- 17:20Preparing Pull Request
- 23:14Successful contribution
- 24:39Results and outcomes
- 26:02Conclusions and advice
related talks
30mMuseum of Weird Bugs: Our Favorites From 8 Years of Service Mesh Debugging
41mDebugging an Application with Service Mesh
20mOverview and State of Linkerd
05mLightning Talk: Locating and Debugging Failures with Linkerd...
39mSeamless multi-cluster Communication and Observability with Linkerd
29mObservability and Debugging Cloud-Native Apps using Linkerd & Conduit
39mObservability to Resolution: The Journey Through a Production K8s Incident
36mWhat WePay Learned From Processing Billions of Dollars on GKE Using Linkerd