MySQL show processlist command details

From: http://www.51testing.com/html/96/110296-69546.html

The output result of the processlist command shows which threads are running. This command can be used to identify problematic query statements.

1. Enter mysqladmin processlist In the MySQL/bin directory;
2. StartMySQL, Enter show processlist;

If you have the super permission, you can see all the threads. Otherwise, you can only see the self-initiated threads (this refers to the thread currently running in the corresponding MySQL account ).

The data format is as follows (only three are intercepted ):

Mysql> show processlist;

+ ----- + ------------- + -------------------- + ------- + --------- + ------- + ---------------------------------- + ----------

| ID | user | host | dB | command | time | state | info

+ ----- + ------------- + -------------------- + ------- + --------- + ------- + ---------------------------------- + ----------

| 207 | root | 192.168.0.20: 51718 | mytest | sleep | 5 | null

| 208 | root | 192.168.0.20: 51719 | mytest | sleep | 5 | null

| 220 | root | 192.168.0.20: 51731 | mytest | query | 84 | locked |

Select bookname, culture, value, type from book where id = 001

Let's briefly describe the meaning and purpose of each column,

The first column, ID, needless to say, is an identifier. It is useful when you want to kill a statement.

The user column displays the user before the ticket. If it is not the root user, this command only displays the SQL statements within your permission range.

Host column, indicating the port from which the statement is sent. Well, it can be used to track users with problematic statements.

DB column to show which process is currently connectedDatabase.

Command column, showing the commands executed by the current connection, which is generally sleep, query, and connect ).

Time column, the duration of this state, in seconds.

The State column displays the status of the SQL statement that uses the current connection. It is an important column and will be described in the future. Note that the State is only a certain State in the statement execution, for an SQL statement that has been queried as an example, it may need to pass through the copying to TMP table, sorting result, sending data and other statuses to complete.

The info column shows this SQL statement. Because the length is limited, the long SQL statement is not displayed completely, but an important basis for determining the problem statement.

The most important part of this command is the State column. MySQL lists the following states:

Checking table
Checking the data table (this is automatic ).
Closing tables
Refreshing the modified data in the table to the disk and closing the used table. This is a very fast operation. If not, check whether the disk space is full or the disk is under a heavy load.
Connect out
The replication slave server is connecting to the master server.
Copying to TMP table on disk
Because the temporary result set is larger than tmp_table_size, the temporary table is being converted from memory storage to disk storage to save memory.
Creating TMP table
Creating a temporary table to store some query results.
Deleting from main table
The server is executing the first part of multi-Table deletion. The first table has just been deleted.
Deleting from reference tables
The server is executing the second part of multi-Table deletion and is deletingOthersTable records.
Flushing tables
Executing flush tables, waiting for other threads to close the data table.
Killed
If a kill request is sent to a thread, the thread will check the kill flag and discard the next kill request. MySQL checks the kill flag in each primary loop. However, in some cases, the thread may die after a short period of time. If the thread is locked by other threads, the kill request will take effect immediately when the lock is released.
Locked
It is locked by other queries.
Sending data
Processing the record of the SELECT query and sending the result to the client.
Sorting for group
Sorting for group.
Sorting for order
Sorting order.
Opening tables
This process should be fast unless it is disturbed by other factors. For example, a data table cannot be opened by another thread before the alter table or lock TABLE statement is executed. Opening a table.
Removing duplicates
A select distinct query is being executed, but MySQL cannot optimize those duplicate records in the previous stage. Therefore, MySQL needs to remove duplicate records and then send the results to the client.
Reopen table
A lock is obtained for a table, but the lock can be obtained only after the table structure is modified. The lock has been released, the data table is closed, and the data table is being re-opened.
Repair by sorting
The repair command is being sorted to create an index.
Repair with keycache
The repair command is using the index cache to create a new index one by one. It is slower than repair by sorting.
Searching rows for update
We are talking about identifying qualified records for updates. It must be completed before the related record is updated.
Sleeping
Waiting for the client to send a new request.
System lock
Waiting for an external system lock to be obtained. If multiple mysqld servers are not running to request the same table at the same time, you can add the -- skip-external-locking parameter to disable External system locks.
Upgrading lock
Insert delayed is trying to get a lock table to insert a new record.
Updating
Searching for matched records and modifying them.
User lock
Waiting for get_lock ().
Waiting for tables
This thread is notified that the data table structure has been modified. You need to re-open the data table to obtain the new structure. Then, in order to re-open the data table, you must wait until all other threads close the table. This notification is generated in the following situations: flush tables tbl_name, alter table, rename table, repair table, analyze table, or optimize table.
Waiting for Handler insert
Insert delayed has completed all the insert operations to be processed and is waiting for new requests.
Most States correspond to fast operations. As long as one thread remains in the same state for several seconds, a problem may occur and you need to check it.
Other statuses are not listed above, but most of them are only needed to check whether there are errors on the server.

The MySQL Manual contains descriptions of all states, links to the following: http://dev.mysql.com/doc/refman/5.0/en/general-thread-states.html

English description from http://www.linuxpk.com/5747.html