Incident Library
Applied filters ComponentDatabaseSymptomThroughput degradationOrganisationeveryClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    The BurstBalance of an RDS instance began to fall rapidly and finally ran out, and the database's performance dropped sharply. The instance ran MySQL 5.7.44 on db.t3.medium with general purpose SSD (gp2) storage of 30GiB.

    Trigger

    A complex SELECT query began writing large amounts of data to temporary tables, which raised WriteIOPS and used up the burst credits.

    Root cause
    Component
    Contributing factor
    Action items
    • Consider tuning the query by reviewing indexes and rewriting it
    • Consider moving the storage from gp2 to gp3 or increasing its size to raise the baseline IOPS
    • Consider adjusting tmp_table_size and max_heap_table_size
    • Consider moving to a more powerful instance type
    • Consider monitoring BurstBalance with CloudWatch alerts and adding external monitoring such as Pingdom
    Lessons

    A complex query can have a large effect on I/O, so database design and queries need continuous improvement, and query performance needs regular monitoring.

Check your cluster for this

This case involves Cloud block storage and Database. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1