She SSH’d into the production database server and ran the usual triage:
It was 2:13 AM on a Tuesday. Maya, the only on-call database engineer, jolted awake by a relentless buzz from her phone.
She typed:
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.”
KILL QUERY 19283; A second later, MySQL responded:
Here’s a short story to illustrate killing a MySQL query in a real-world scenario.
SHOW PROCESSLIST; The output flooded her screen. Dozens of connections. Most were sleeping. But one caught her eye:
Killing it was the only immediate option. No time for a graceful shutdown.
She SSH’d into the production database server and ran the usual triage:
It was 2:13 AM on a Tuesday. Maya, the only on-call database engineer, jolted awake by a relentless buzz from her phone.
She typed:
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.”
KILL QUERY 19283; A second later, MySQL responded:
Here’s a short story to illustrate killing a MySQL query in a real-world scenario.
SHOW PROCESSLIST; The output flooded her screen. Dozens of connections. Most were sleeping. But one caught her eye:
Killing it was the only immediate option. No time for a graceful shutdown.