Incident Library

Organisation

Repro

Repro · repro

2 cases · 2019 to 2024

Root cause Capacity exhaustion1Breaking change in an upgrade1
Component Database2Database replication1
Contributing factor Monitoring blind spot1Unrepresentative staging1
Symptom Connection resets1High error rate1High latency1Replication lag1Throughput degradation1

Cases

  1. IL-0444 Reader connections to Repro's Aurora MySQL cluster were cut with Lost connection errors every time ALTER TABLE ranRepro · 2024

    Root cause Breaking change in an upgrade

  2. IL-0443 A Repro Aurora MySQL reader restarted unexpectedly and writer insert latency rose about sevenfold for a day or moreRepro · 2019

    Root cause Capacity exhaustion