CDChief Debuggerintech.kompress.ai·2h ago · 6 min readThe Bug That Only Showed Up After a Week: Why We Still Needed to Add a Daily VACUUMThe first two posts in this series were about a dramatic redesign and an even more dramatic night of debugging. This one is different. There was no outage. No paging. No 1 AM EXPLAIN ANALYZE session u00
CDChief Debuggerintech.kompress.ai·Jun 20 · 10 min readPart 3: Building a Cluster That Manages ItselfBy the end of Part 2, the tombstone math was understood. Device-A's write frequency was a fixed cost. Device-B's TTL had been cut 3×. Device-C's reconnect dump had a calendared expiry date. None of th00
CDChief Debuggerintech.kompress.ai·Jun 19 · 8 min readPart 2: When 0% Tombstones Is Not the Finish Line"The compaction had worked. The timing had not. This is the part of the story that rarely gets written about, because it happens after the blog post that covers the migration. The migration was the rig30
CDChief Debuggerintech.kompress.ai·Jun 15 · 11 min readPart 1: When Your Time-Series Data Turns Against You...Migrating 3.9 Billion Rows to TWCS Without Downtime on a Constrained IoT Cluster The number that started everything was 7.99 ms. That was the average read latency on our Cassandra keyspace — a cluster00
CDChief Debuggerintech.kompress.ai·Jun 11 · 9 min readWhen Your Fix Creates a New Problem: Debugging the Production Partition MigrationThe migration went live just after midnight. The tables were renamed. The application restarted. Everything looked fine. By 1 AM, the sync job — the background process that marks rows as processed and01R
