MySQL show status Parameter Details, mysqlstatus

Source: Internet
Author: User
Tags ssl connection

MySQL show status Parameter Details, mysqlstatus

Status name Scope Detailed explanation
Aborted_clients Global Number of connections that are interrupted due to Client termination because the client does not properly close the connection
Aborted_connects Global Number of connections that fail to connect to the MySQL server
Binlog_cache_disk_use Global The number of transactions that use the temporary binary log cache but exceed the binlog_cache_size value, and use the temporary file to save the statements in the transaction
Binlog_cache_use Global Number of transactions cached using temporary binary logs
Bytes_received Both The number of bytes received from all clients.
Bytes_sent Both The number of bytes sent to all clients.
Com *   Number of Database Operations
Compression Session Only enable the compression protocol between the client and the server
Connections Global Number of connections attempting to connect (whether or not successful) to the MySQL server
Created_tmp_disk_tables Both Number of temporary tables automatically created on the hard disk when the server executes the statement
Created_tmp_files Global Number of temporary files created by mysqld
Created_tmp_tables Both The number of temporary tables in memory automatically created when the server executes the statement. If Created_tmp_disk_tables is large, you may need to increase the tmp_table_size value so that the temporary table is based on memory instead of Hard Disk
Delayed_errors Global The number of wrong lines written with insert delayed (which can be duplicate key ).
Delayed_insert_threads Global The number of insert delayed processor threads used.
Delayed_writes Global Number of insert delayed rows written
Flush_commands Global Number of FLUSH statements executed.
Handler_commit Both Number of internal statement submissions
Handler_delete Both Number of times a row is deleted from a table.
Handler_discover Both The MySQL server can ask whether the ndb cluster Storage engine knows a table with a certain name. This is called discovery. Handler_discover indicates the number of times this method is used to discover.
Handler_prepare Both A counter for the prepare phase of two-phase commit operations.
Handler_read_first Both The number of times the first index is read. If it is high, it is recommended that the server perform a large number of full index scans. For example, SELECT col1 FROM foo, assuming that col1 has an index.
Handler_read_key Both The number of requests that read a row based on the key. If the index is high, the query and table index are correct.
Handler_read_next Both Number of requests read from the next row in the key-ordered order. This value increases if you use range constraints or if you perform an index scan to query index columns.
Handler_read_prev Both The number of requests read from the previous row in a key-ordered manner. This read method is mainly used to optimize order by... DESC.
Handler_read_rnd Both The number of requests reading a row at a fixed position. If you are executing a large number of queries and want to sort the results, this value is high. You may have used a large number of queries that require MySQL to scan the entire table or your connection does not properly use the key.
Handler_read_rnd_next Both The number of requests read from the next row in the data file. If you are performing a large number of table scans, this value is high. It usually indicates that your table index is incorrect or the written query does not use the index.
Handler_read_prev Both The number of requests read from the previous row in a key-ordered manner. This read method is mainly used to optimize order by... DESC.
Handler_read_rnd Both The number of requests reading a row at a fixed position. If you are executing a large number of queries and want to sort the results, this value is high. You may have used a large number of queries that require MySQL to scan the entire table or your connection does not properly use the key.
Handler_read_rnd_next Both The number of requests read from the next row in the data file. If you are performing a large number of table scans, this value is high. It usually indicates that your table index is incorrect or the written query does not use the index.
Handler_rollback Both The number of internal ROLLBACK statements.
Handler_savepoint Both The number of requests that place a storage point in a storage engine.
Handler_savepoint_rollback Both In the request of a storage engine, roll back to the number of storage points.
Handler_update Both Number of requests for updating a row in the table.
Handler_write Both The number of requests to insert a row into the table.
Innodb_buffer_pool_pages_data Global The number of pages (dirty or clean) that contain data ).
Innodb_buffer_pool_pages_total Global Total buffer pool size (number of pages ).
Innodb_buffer_pool_read_ahead_rnd Global The number of random read-aheads initialized by InnoDB. This occurs when a query scans a large portion of a table in a random order.
Innodb_buffer_pool_read_ahead_seq Global The number of InnoDB-initiated sequential read-aheads. This occurs when InnoDB performs a full table scan in sequence.
Innodb_buffer_pool_read_requests Global Number of logical read requests completed by InnoDB.
Innodb_buffer_pool_reads Global The number of logical reads in the buffer pool that InnoDB must read on a single page cannot be met.
Innodb_buffer_pool_wait_free Global Generally, data is written to the InnoDB buffer pool through the background. However, if you want to read or create a page without a clean page available, you still need to wait for the page to be cleared. This counter counts the waiting instance. If the buffer pool size has been properly set, this value should be small.
Innodb_buffer_pool_write_requests Global Number of writes to the InnoDB buffer pool.
Innodb_data_fsyncs Global Fsync () operations.
Innodb_data_pending_fsyncs Global The number of fsync () operations currently suspended.
Innodb_data_pending_reads Global The currently suspended reading.
Innodb_data_pending_writes Global Number of currently suspended writes.
Innodb_data_read Global The amount of data that has been read (in bytes ).
Innodb_data_reads Global Total number of data reads.
Innodb_data_writes Global Total number of data writes.
Innodb_data_written Global The data size (in bytes) that has been written so far ).
Innodb_dblwr_pages_written Global Number of Dual-write operations performed
Innodb_dblwr_writes Global Number of pages written for the double write operation
Innodb_log_waits Global We have to wait for the time. Because the log buffer is too small, we must wait for it to be cleared before continuing.
Innodb_log_write_requests Global Number of log write requests.
Innodb_log_writes Global The number of physical writes to log files.
Innodb_ OS _log_fsyncs Global Number of fsync () writes to log files.
Innodb_ OS _log_pending_fsyncs Global Number of pending Log File fsync () operations.
Innodb_ OS _log_pending_writes Global Pending log file write operations
Innodb_ OS _log_written Global The number of bytes written to the log file.
Innodb_page_size Global Size of the compiled InnoDB page (16 KB by default ). Many values are counted by pages. The page size is easily converted to bytes.
Innodb_pages_created Global The number of pages created.
Innodb_pages_read Global The number of pages read.
Innodb_pages_written Global The number of pages written.
Innodb_row_lock_current_waits Global The number of rows to be locked.
Innodb_row_lock_time Global Total time spent on row locking, in milliseconds.
Innodb_row_lock_time_avg Global The average time of row locking, in milliseconds.
Innodb_row_lock_time_max Global The maximum row lock time, in milliseconds.
Innodb_row_lock_waits Global The number of times a row is locked.
Innodb_rows_deleted Global The number of rows deleted from the InnoDB table.
Innodb_rows_inserted Global The number of rows inserted to the InnoDB table.
Innodb_rows_read Global The number of rows read from the InnoDB table.
Innodb_rows_updated Global The number of rows updated in the InnoDB table.
Key_blocks_not_flushed Global The number of data blocks that have been changed in the key cache but have not been cleared to the hard disk.
Key_blocks_unused Global Number of unused blocks in the key cache. You can use this value to determine how many key caches are used.
Key_blocks_used Global Number of Blocks Used in the key cache. This value is a high-level mark, indicating the maximum number of blocks used at the same time.
Key_read_requests Global The number of data block requests from the cache read key.
Key_reads Global The number of data blocks read from the hard disk. If Key_reads is large, the value of Key_buffer_size may be too small. You can use Key_reads/Key_read_requests to calculate the cache loss rate.
Key_write_requests Global Number of requests that write the data block of the Key to the cache.
Key_writes Global The number of physical writes to the data block that writes the key to the hard disk.
Last_query_cost Session The total cost of the final compiled query calculated by the query optimizer. Compare the costs of different query schemes for the same query. The default value 0 indicates that no compilation query exists. The default value is 0. Last_query_cost has a session range.
Max_used_connections Global The maximum number of connections that are used at the same time after the server is started.
Ndb *   Ndb cluster problems
Open_files Global Number of opened files
Not_flushed_delayed_rows Global The number of rows waiting to be written to the insert delay queue.
Open_streams Global The number of opened streams (mainly used for recording ).
Open_table_definitions Global Number of cached. frm files
Open_tables Both The number of opened tables.
Opened_files Global The number of opened files. Does not include files of other types such as sockets or pipelines. It does not include the files that the storage engine uses for its own internal functions.
Opened_table_definitions Both Number of cached. frm files
Opened_tables Both The number of opened tables. If Opened_tables is large, the table_cache value may be too small.
Prepared_stmt_count Global The number of current pre-processing statements. (Maximum number of system variables: max_prepared_stmt_count)
Qcache_free_blocks Global Queries the number of free memory blocks in the cache.
Qcache_free_memory Global Queries the number of free memory cached.
Qcache_hits Global Queries the number of times the cache is accessed.
Qcache_inserts Global The number of queries added to the cache.
Qcache_lowmem_prunes Global Because the memory is small, the number of queries deleted from the cache is.
Qcache_not_cached Global Number of non-Cache queries (not cached, or not cached due to the query_cache_type setting value ).
Qcache_queries_in_cache Global The number of queries registered to the cache.
Qcache_total_blocks Global Queries the total number of blocks in the cache.
Queries Both The number of requests executed by the server, including the requests in the stored procedure.
Questions Both The number of queries sent to the server.
Rpl_status Global Failed Security replication status (not in use ).
Select_full_join Both The number of joins without indexes. If the value is not 0, check the index carefully.
Select_full_range_join Both The number of connections that use range search in the referenced table.
Select_range Both The number of connections that use the range in the first table. Generally, this is not a key issue, even if the value is large.
Select_range_check Both The number of connections without a key value that check the key value after each row of data. If the value is not 0, check the index carefully.
Select_scan Both The number of connections that completely scan the first table.
Slave_heartbeat_period Global Replication heartbeat Interval
Slave_open_temp_tables Global Number of temporary tables opened from the server
Slave_received_heartbeats Global Slave server heartbeat count
Slave_retried_transactions Global Number of retries from the Server replication thread since this startup
Slave_running Global If the server is connected to the master server's slave server, the value is ON.
Slow_launch_threads Both The number of threads created when slow_launch_time is exceeded.
Slow_queries Both The number of queries whose query time exceeds long_query_time.
Sort_merge_passes Both The number of merge executed by the sorting algorithm. If the value of this variable is large, you should consider increasing the value of the sort_buffer_size system variable.
Sort_range Both The number of sorting tasks in the specified range.
Sort_rows Both Number of sorted rows.
Sort_scan Both The number of sorting completed by scanning the table.
Ssl *   Ssl connection problems
Table_locks_immediate Global The number of times the table lock is obtained immediately.
Table_locks_waited Global The number of table locks that cannot be obtained immediately. If the value is high and there are performance problems, you should first optimize the query and then split the table or use replication.
Threads_cached Global The number of threads in the thread cache.
Threads_connected Global The number of currently opened connections.
Threads_created Global Number of threads used to process connections. If Threads_created is large, you may need to increase the value of thread_cache_size. The cache renewal rate is calculated using Threads_created/Connections.
Threads_running Global Number of activated (non-sleep) threads.
Uptime Global The time when the server is running (in seconds ).
Uptime_since_flush_status Global The last time the flush status was used (in seconds ).

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.