New smo search site! HERE
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%. The API errors stopped. Her phone went quiet.
She groggily opened her laptop, heart already racing. The company’s main e-commerce site was slowing to a crawl. Users couldn’t load their carts. mysql kill a query
Almost six minutes. That single query was hogging the CPU, locking critical rows, and starving the checkout service.
KILL QUERY 19283; A second later, MySQL responded: The API errors stopped
| 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%' |
It was 2:13 AM on a Tuesday. Maya, the only on-call database engineer, jolted awake by a relentless buzz from her phone. The company’s main e-commerce site was slowing to a crawl
SHOW PROCESSLIST; The output flooded her screen. Dozens of connections. Most were sleeping. But one caught her eye: