Incident Library?

Incident Library?

Component ?

HAProxy HAProxy · `haproxy`

2 cases · 2019 to 2020

Root cause ?Capacity exhaustion 1 Software defect 1

Contributing factor ?Unverified assumption 1 Ignored early signal 1 Unknown limit 1 No capacity planning 1 Unrepresentative staging 1

Symptom ?Intermittent connection failures 2 Connection resets 1 High error rate 1 High latency 1 OOMKilled 1 Load imbalance 1

Cases, by severity

IL-0011 Sorted HAProxy backends sent every request to the same first pod — Skyscanner, 2019, sev2
Root cause Software defect
IL-0013 Connection resets from a full conntrack table on GKE nodes — loveholidays, 2020
Root cause Capacity exhaustion

View on the graph