🔒 Paid

Write Amplification from Misconfigured Storage Compaction

Disk IOPS utilization and write latency have both spiked during a routine, unremarkable traffic increase. Nothing about the storage engine's deployment or configuration changed today — but something did change three weeks ago: a compaction tuning parameter that quietly raised write amplification without ever crossing an alert threshold on its own. The traffic bump didn't cause this; it only exposed headroom that was already gone. Diagnose the configuration root cause rather than treating this as a simple capacity problem.

Difficulty
Senior Staff
Expected Time
~20 min
Category
Databases & Storage

Skills

  • Distinguishing a demand-driven capacity problem from a configuration-driven amplification problem
  • Reading write amplification and compaction backlog as leading indicators, not just disk IOPS
  • Recognizing a plausible-but-inferior capacity-scaling remediation that masks rather than fixes the cause
  • Investigating configuration change history, not just current deploys, when nothing obviously changed today

System Architecture

  • Write API
  • Storage Engine (LSM Compaction)
  • Block Storage (Disk IOPS)
  • Storage Config Service

This is a Pro scenario. Upgrade to Pro to unlock it.

Upgrade to ProBack to Incidents