SELECT CONCAT('KILL ', id, ';') AS kill_command FROM information_schema.processlist WHERE command != 'Sleep' AND time > 300; -- 5+ minutes Copy the output and run the commands. DELIMITER $$ CREATE PROCEDURE kill_long_running_queries(IN max_time_seconds INT) BEGIN DECLARE done INT DEFAULT FALSE; DECLARE pid INT; DECLARE cur CURSOR FOR SELECT id FROM information_schema.processlist WHERE command != 'Sleep' AND time > max_time_seconds; DECLARE CONTINUE HANDLER FOR NOT FOUND SET done = TRUE; OPEN cur; read_loop: LOOP FETCH cur INTO pid; IF done THEN LEAVE read_loop; END IF; SET @kill_stmt = CONCAT('KILL ', pid); PREPARE stmt FROM @kill_stmt; EXECUTE stmt; DEALLOCATE PREPARE stmt; END LOOP; CLOSE cur; END$$ DELIMITER ;
SET GLOBAL max_execution_time = 30000; -- milliseconds (30 seconds) Or per session/query:
KILL 12345; Generate kill commands for all queries exceeding a threshold: mysql kill long running queries
KILL QUERY <id>; Example:
Long-running queries can cripple your database performance, consume server resources, and lead to application timeouts. Here’s how to spot and terminate them in MySQL. First, check which queries are running longer than acceptable. SELECT CONCAT('KILL ', id, ';') AS kill_command FROM
-- Usage CALL kill_long_running_queries(120); -- kills queries running > 2 minutes Instead of just killing queries, prevent them from running too long:
KILL [CONNECTION] <id>; Or if you only want to terminate the current query but keep the connection: First, check which queries are running longer than
How to Identify and Kill Long-Running Queries in MySQL
