Mysql_ "MySQL" Common MySQL process state

The analyzing thread is an analysis of the statistics of the MyISAM table (for example, ANALYZE table). The checking permissions thread is the one that checks whether the server has the required permissions to execute the statement. The Checking table thread is performing a form check operation. The cleaning up thread processes a command and is preparing to free up memory and reset certain state variables. The closing tables thread is a table that changes the data in the table to flush to disk and close the use. This should be a quick operation. If not, you should make sure that you do not have a full disk and disk that is not used in very heavy situations. The converting HEAP to MyISAM thread is a table of memory table disks MyISAM from the internal temporal table of the conversion. Copy to TMP table line is impersonating is processing an ALTER TABLE statement. After this state occurs, the table with the new structure is created, but the forward copy is copied to it. Copying to Group table if the statement has different order by and group by criteria, the rows sorted by group are copied to a temporary table. The Copying to TMP table server is copied to the in-memory temporary tables. The Copying to TMP table on disk server is copied to a temporary table on disks. The temporary result set has become too large (see section 7.8.4, "How MySQL uses internal temporary tables"). Therefore, the thread is based on the disk format of the temporary table in memory to save memory. Creating Index line is impersonating in process alter TABLE ... ENABLE KEYS ALTER TABLE ... The ENABLE keys is the MyISAM MyISAM table. Creating Sort index line is impersonating in processing a select is resolved using an internal temp table. Creating table thread to create one. This includes creating temporary tables. The Creating TMP table thread is creating a temporary table in memory or on disk. If the table is created in memory but is later converted to a table on a disk, the operation of the copying to TMP table on disk. Deleting from Main Table server is performing the first part of multiple table deletions. It can only be removed from the first table, and the columns are saved and removed from the other table (reference) offset. Deleting from reference tables The server is performing the second part of multiple table deletions, removing the matching rows from the other tables. Discard_or_import_Tablespace line is impersonating in processing an alter TABLE ... DISCARD tablespace ALTER TABLE ... DISCARD tablespace or alter TABLE ... IMPORT tablespace ALTER TABLE ... IMPORT tablespace statement. End this occurs before the end of the cleanup alter TABLE, CREATE VIEW, DELETE, INSERT, select, or UPDATE statement. The executing thread has started executing the statement. Execution of Init_command threads are executing value statements in Init_command system variables. Freeing the commands that the items thread has executed. Release some of the items that are completed in this state, involving the query cache. This state is usually followed by cleaning up. Flushing TABLES thread is executing flush TABLES, waiting for all threads to close their tables. Fulltext initialization the server is ready to perform a full-text search of a natural language. Init this occurs before the initialization of the alter TABLE, DELETE, INSERT, select, or UPDATE statement. The actions taken by the server in this state include flushing the InnoDB log in the binary log, and some query cache cleanup operations. For the end state, the following actions may occur: After you change the cache entry for a data query in the Delete table, write an event in the binary log to release the memory buffer, including the statement that the blob killed someone sent a kill thread, and it should abort the kill flag at the next check. Check that the flag is the primary loop in each MySQL, but in some cases it may also take a short time for the thread to die. If the thread is locked by another thread, kill other threads that are in effect as soon as possible to release its lock. The locked query is locked by another query. Logging slow query thread is writing a statement that queries the log slowly. Null This state is used for the show processlist state. Login connects the initial state of the thread until the client has successfully authenticated. Opening tables, Opening table thread tries to open a table. This should be very fast in the process unless there is a block to open. For example, an ALTER TABLE or LOCK TABLE statement can prevent a statement from opening a table until it is complete. Your Table_cache value is big enough, which is also worth a try. OptimThe izing server performs the initial optimization of the query. Preparing this state appears in the query optimization process. Purging old relay logs thread is the elimination of unnecessary trunk log files. Query end This state occurs after the processing of queries, but in this freeing item state of items. The Reading from NET Server is read from a network packet. Removing duplicates queries using select distinct in such a way that MySQL cannot optimize out of different operations in the early stages. Because of this, MySQL needs an extra stage to delete all duplicate rows before sending the results to the client. The removing TMP table thread is the internal Select Table SELECT statement after the elimination process. If no temporary table is created, this state is not used. Rename line thread Name table. Rename result table line is impersonating processes an ALTER TABLE statement, creates a new table, and renames it to replace the original table. Reopen tables thread has a table lock, but notice that the underlying table structure changes after the lock. It releases the lock, closes the table, and tries to reopen it. Repair by sorting fix code is to use sort to create an index. Repair done the thread has completed a multithreaded MyISAM table. The Repair with Keycache repair code is used to create the key through the key cache. This is much higher than the speed repair by sorting to sort. Rolling the back thread to rollback the transaction. Saving state such as repairing or analyzing myisam MyISAM table operations, the thread is the status of a new table that is energy-efficient. Myi file header. Countries include the number of rows, such as information auto_increment counters, as well as key distributions. Searching rows for update threads are doing the first phase of the update before they find all matching rows. The work to be done, update update is changing, is used to find the index of the row involved. The sending data thread processes a SELECT statement line and sends the information to the client. Because operations that occur in this state tend to perform a large amount of disk access (read), it is often the longest running state in a given query's life cycle. The setup thread begins an ALTER TABLE operation. The sorting for group thread is doing a classification to group by. The sorting for order thread is done to satisfy the order by ordering. Sorting index thread to sort indexes the page, higherEfficient access to MyISAM table optimization operations. Sorting result for the SELECT statement, which is creating sort index similar to But Nontemporary table. The statistics server calculates the statistics to develop a query execution plan. If a thread is in this state for a long time, the server may be disk bound to perform other work. System lock the thread will either require or is waiting for an internal or external lock table. If this status is caused by an external lock request and you do not use multiple mysqld access to the same MyISAM MyISAM table, you can disable the lock option with the external System--skip-external-locking. However, external locking is disabled by default, so this option is likely to have no effect. SHOW profile, this state means that the thread requests the lock (not waiting). The next thread state after Table lock is locked by system lock. The thread has acquired an external lock and requires an internal table lock. Updating threads are looking for rows to update and update them. Updating Main Table server is performing the first part of a multi-table update. It is only updating the first table and saving the columns and for updating other table (reference) offsets. Updating reference Tables server is performing the second part of multiple table updates and updating rows that match from other tables. The User lock thread requests or asks for a get_lock () call with a consultation lock. SHOW profile, this state means that the thread requests the lock (not waiting). The waiting for release of the Readlock thread is being released while waiting for another thread (with the global read lock flush TABLES with read lock TABLES). Waiting for tables, the waiting for table thread gets a notification that the basic structure of a table has changed, and it needs to reopen the table to get the new structure. However, to reopen the table, it must wait until all other threads have closed the problem in the table. This notification occurs if another thread has flush TABLES or one of the following statements on the table flush TABLES tbl_name tbl_name ALTER table, RENAME table Table REPAIR Table table ANALYZE table table, OPTIMIZE table table. Waiting on cond in which the thread is waiting for a condition to become a real generalState. No specific status information is available. The waiting to get Readlock thread has issued a flush TABLES with the Read lock statement to obtain a global read lock and is waiting to acquire the lock. The Writing to NET Server writes a packet to the network.

Mysql_ "MySQL" common MySQL process state