It was 2:13 AM on a Tuesday. Maya, the only on-call database engineer, jolted awake by a relentless buzz from her phone.
Killing it was the only immediate option. No time for a graceful shutdown. 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.” It was 2:13 AM on a Tuesday
She typed:
-- Find long-running queries SELECT id, user, time, state, info FROM information_schema.PROCESSLIST WHERE command != 'Sleep' AND time > 60; -- Kill one KILL QUERY <id>; No time for a graceful shutdown
Here’s a short story to illustrate killing a MySQL query in a real-world scenario.
The next morning, Maya added a monitoring alert for queries running longer than 60 seconds. She also taught the dev team how to catch themselves: