DE

↑ ↓ select, Enter open, Esc close

Kill a hanging MySQL query

caution rootMySQL and MariaDBdebian, ubuntu

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
root@server
mysql -e 'KILL 12345;'

Terminates the connection with the given ID, including its running query. The ID comes from the process list. Useful when a single query locks tables and blocks all other access.

Note: An aborted write transaction is rolled back, which can itself take a while for large changes. KILL QUERY only aborts the query and keeps the connection open.

Also searched as

  • kill mysql query
  • kill mysql process
  • database query stuck

Related one-liners

All in MySQL and MariaDB

Show running MySQL queries without idle connections

#mysql -e "SELECT id, user, db, time, state, LEFT(info, 100) AS query FROM information_schema.processlist WHERE command <> 'Sleep' ORDER BY time DESC;"
harmlessMySQL and MariaDB

Analyze the slow query log for the slowest queries

#mysqldumpslow -s t -t 10 /var/log/mysql/mariadb-slow.log
harmlessMySQL and MariaDB

Back up a single database consistently as gzip

$mysqldump --single-transaction --quick -u dbuser -p wp_example | gzip > /var/www/vhosts/example.com/wp_example.sql.gz
harmlessMySQL and MariaDB

Back up all databases into one gzipped file

#mysqldump --single-transaction --quick --all-databases --routines --events | gzip > /root/all-databases.sql.gz
harmlessMySQL and MariaDB

Back up each database into its own gzipped file

#for db in $(mysql -NBe 'SHOW DATABASES' | grep -Ev '^(information_schema|performance_schema|sys)$'); do mysqldump --single-transaction --quick "$db" | gzip > "/root/db-backup/$db.sql.gz"; done
harmlessMySQL and MariaDB

Check all MySQL tables for errors

#mysqlcheck --all-databases --check --silent
harmlessMySQL and MariaDB

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.