General Thread States
This article documents the major general thread states. More specific lists related to delayed inserts, replication, the query cache and the event scheduler are listed in:
- Event Scheduler Thread States
- Query Cache Thread States
- Master Thread States
- Slave Connection Thread States
- Slave I/O Thread States
- Slave SQL Thread States
These correspond to the STATE values listed by the SHOW PROCESSLIST statement or in the Information Schema PROCESSLIST Table as well as the PROCESSLIST_STATE value listed in the Performance Schema threads Table
| Value | Description |
|---|---|
| After create | The function that created (or tried to create) a table (temporary or non-temporary) has just ended. |
| Analyzing | Calculating table key distributions, such as when running an ANALYZE TABLE statement. |
| checking permissions | Checking to see whether the permissions are adequate to perform the statement. |
| Checking table | Checking the table. |
| cleaning up | Preparing to reset state variables and free memory after executing a command. |
| closing tables | Flushing the changes to disk and closing the table. This state will only persist if the disk is full or under extremely high load. |
| converting HEAP to Aria | Converting an internal MEMORY temporary table into an on-disk Aria temporary table. |
| converting HEAP to MyISAM | Converting an internal MEMORY temporary table into an on-disk MyISAM temporary table. |
| copy to tmp table | A new table has been created as part of an ALTER TABLE statement, and rows are about to be copied into it. |
| Copying to group table | Sorting the rows by group and copying to a temporary table, which occurs when a statement has different GROUP BY and ORDER BY criteria. |
| Copying to tmp table | Copying to a temporary table in memory. |
| Copying to tmp table on disk | Copying to a temporary table on disk, as the resultset is too large to fit into memory. |
| Creating index | Processing an ALTER TABLE ... ENABLE KEYS for an Aria or MyISAM table. |
| Creating sort index | Processing a SELECT statement resolved using an internal temporary table. |
| creating table | Creating a table (temporary or non-temporary). |
| Creating tmp table | Creating a temporary table (in memory or on-disk). |
| deleting from main table | Deleting from the first table in a multi-table delete, saving columns and offsets for use in deleting from the other tables. |
| deleting from reference tables | Deleting matched rows from secondary reference tables as part of a multi-table delete. |
| discard_or_import_tablespace | Processing an ALTER TABLE ... IMPORT TABLESPACE or ALTER TABLE ... DISCARD TABLESPACE statement. |
| end | State before the final cleanup of an ALTER TABLE, CREATE VIEW, DELETE, INSERT, SELECT, or UPDATE statement. |
| executing | Executing a statement. |
| Execution of init_command | Executing statements specified by the --init_command mariadb client option. |
| filling schema table | A table in the information_schema database is being built. |
| freeing items | Freeing items from the query cache after executing a command. Usually followed by the cleaning up state. |
| Flushing tables | Executing a FLUSH TABLES statement and waiting for other threads to close their tables. |
| FULLTEXT initialization | Preparing to run a full-text search. This includes running the fulltext search (MATCH ... AGAINST) and creating a list of the result in memory |
| init | About to initialize an ALTER TABLE, DELETE, INSERT, SELECT, or UPDATE statement. Could be performaing query cache cleanup, or flushing the binary log or InnoDB log. |
| Killed | Thread will abort next time it checks the kill flag. Requires waiting for any locks to be released. |
| Locked | Query has been locked by another query. |
| logging slow query | Writing statement to the slow query log. |
| NULL | State used for SHOW PROCESSLIST. |
| login | Connection thread has not yet been authenticated. |
| manage keys | Enabling or disabling a table index. |
| Opening table[s] | Trying to open a table. Usually very quick unless the limit set by table_open_cache has been reached, or an ALTER TABLE or LOCK TABLE is in progress. |
| optimizing | Server is performing initial optimizations in for a query. |
| preparing | State occurring during query optimization. |
| Purging old relay logs | Relay logs that are no longer needed are being removed. |
| query end | Query has finished being processed, but items have not yet been freed (the freeing items state. |
| Reading file | Server is reading the file (for example during LOAD DATA INFILE). |
| Reading from net | Server is reading a network packet. |
| Removing duplicates | Duplicated rows being removed before sending to the client. This happens when SELECT DISTINCT is used in a way that the distinct operation could not be optimized at an earlier point. |
| removing tmp table | Removing an internal temporary table after processing a SELECT statement. |
| rename | Renaming a table. |
| rename result table | Renaming a table that results from an ALTER TABLE statement having created a new table. |
| Reopen tables | Table is being re-opened after thread obtained a lock but the underlying table structure had changed, so the lock was released. |
| Repair by sorting | Indexes are being created with the use of a sort. Much faster than the related Repair with keycache. |
| Repair done | Multi-threaded repair has been completed. |
| Repair with keycache | Indexes are being created through the key cache, one-by-one. Much slower than the related Repair by sorting. |
| Rolling back | A transaction is being rolled back. |
| Saving state | New table state is being saved. For example, after, analyzing a MyISAM table, the key distributions, rowcount etc. are saved to the .MYI file. |
| Searching rows for update | Finding matching rows before performing an UPDATE, which is needed when the UPDATE would change the index used for the UPDATE |
| Sending data | Sending data to the client as part of processing a SELECT statement or other statements that returns data like INSERT ... RETURNING . Often the longest-occurring state as it also include all reading from tables and disk read activities. Where an aggregation or un-indexed filtering occurs there is significantly more rows read than what is sent to the client. |
| setup | Setting up an ALTER TABLE operation. |
| Sorting for group | Sorting as part of a GROUP BY |
| Sorting for order | Sorting as part of an ORDER BY |
| Sorting index | Sorting index pages as part of a table optimization operation. |
| Sorting result | Processing a SELECT statement using a non-temporary table. |
| statistics | Calculating statistics as part of deciding on a query execution plan. Usually a brief state unless the server is disk-bound. |
| System lock | Requesting or waiting for an external lock for a specific table. The storage engine determines what kind of external lock to use. For example, the MyISAM storage engine uses file-based locks. However, MyISAM's external locks are disabled by default, due to the default value of the skip_external_locking system variable. Transactional storage engines such as InnoDB also register the transaction or statement with MariaDB's transaction coordinator while in this thread state. See MDEV-19391 for more information about that. |
| Table lock | About to request a table's internal lock after acquiring the table's external lock. This thread state occurs after the System lock thread state. |
| update | About to start updating table. |
| Updating | Searching for and updating rows in a table. |
| updating main table | Updating the first table in a multi-table update, and saving columns and offsets for use in the other tables. |
| updating reference tables | Updating the secondary (reference) tables in a multi-table update |
| updating status | This state occurs after a query's execution is complete. If the query's execution time exceeds long_query_time, then Slow_queries is incremented, and if the slow query log is enabled, then the query is logged. If the SERVER_AUDIT plugin is enabled, then the query is also logged into the audit log at this stage. If the userstats plugin is enabled, then CPU statistics are also updated at this stage. |
| User lock | About to request or waiting for an advisory lock from a GET LOCK() call. For SHOW PROFILE, means requesting a lock only. |
| User sleep | A SLEEP() call has been invoked. |
| Waiting for commit lock | FLUSH TABLES WITH READ LOCK is waiting for a commit lock, or a statement resulting in an explicit or implicit commit is waiting for a read lock to be released. This state was called Waiting for all running commits to finish in earlier versions. |
| Waiting for global read lock | Waiting for a global read lock. |
| Waiting for table level lock | External lock acquired,and internal lock about to be requested. Occurs after the System lock state. In earlier versions, this was called Table lock. |
| Waiting for xx lock | Waiting to obtain a lock of type xx. |
| Waiting on cond | Waiting for an unspecified condition to occur. |
| Writing to net | Writing a packet to the network. |
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
