Almost instantly, CPU usage dropped from 98% to 12%. The API errors stopped. Her phone went quiet.
Query OK, 0 rows affected (0.00 sec) She ran SHOW PROCESSLIST again. The row with Id 19283 was gone — replaced by a single line: KILLED (for a brief moment, then disappeared). mysql kill a query
KILL <connection_id>; -- kills the entire connection, not just the query She never forgot that 2 AM wakeup. And from then on, every SELECT on large tables had to justify its indexes in the design review. “With great SELECT comes great responsibility — and the ability to KILL QUERY when responsibility fails.” Almost instantly, CPU usage dropped from 98% to 12%
| Id | User | Host | db | Command | Time | State | Info | |----|------|------|----|---------|------|-------|------| | 19283 | app_user | 10.2.3.4:54321 | shop | Query | 347 | Sending data | SELECT * FROM orders o JOIN order_items oi ON o.id = oi.order_id JOIN products p ON oi.product_id = p.id WHERE o.created_at > '2023-01-01' AND p.tags LIKE '%summer%' | Query OK, 0 rows affected (0