General Thread States The server is executing the first part of a multiple-table delete. It is deleting only from the first table, and saving columns and offsets to be used for deleting from the other (reference) tables. •  deleting from reference tables •  discard_or_import_tablespace •  end The server is executing the second part of a multiple-table delete and deleting the matched rows from the other tables. The thread is processing an  ALTER TABLE ... DISCARD TABLESPACE  or  ALTER TABLE ... IMPORT TABLESPACE  statement. This occurs at the end but before the cleanup of  ALTER TABLE ,  CREATE VIEW ,  DELETE ,  INSERT , SELECT , or  UPDATE  statements. •Writing an event to the binary log •Freeing memory buffers, including for blobs •  executing For the  end  state, the following operations could be happening: The thread has begun executing a statement. •  Execution of init_command •  freeing items The thread is executing statements in the value of the  init_command  system variable. The thread has executed a command. This state is usually followed by  cleaning up . The server is preparing to perform a natural-language full-text search. This occurs before the initialization of  ALTER TABLE ,  DELETE ,  INSERT ,  SELECT , or  UPDATE statements. Actions taken by the server in this state include flushing the binary log and the  InnoDB  log. •  init •  FULLTEXT initialization •  Killed Someone has sent a  KILL  statement to the thread and it should abort next time it checks the kill flag. The flag is checked in each major loop in MySQL, but in some cases it might still take a short time for the thread to die. If the thread is locked by some other thread, the kill takes effect as soon as the other thread releases its lock. The thread is trying to lock a system table (for example, a time zone or log table). The thread is writing a statement to the slow-query log. •  logging slow query •  Locking system tables 1849