In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-03-26 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
The number of Aborted_clients connections that were interrupted due to client termination because the client did not close the connection correctly
The number of failed connections that Aborted_connects attempted to connect to the MySQL server
The number of transactions in which Binlog_cache_disk_use uses a temporary binary log cache but exceeds the binlog_cache_ size value and uses temporary files to save statements in the transaction
Number of transactions that Binlog_cache_use uses temporary binary log caching
The number of bytes received by Bytes_received from all clients.
The number of bytes sent by Bytes_sent to all clients.
Number of com_* various database operations
Only compression protocol is enabled between Compression client and server
The number of connections Connections attempted to connect to the MySQL server, whether successful or not
The number of temporary tables automatically created on the hard disk when the Created_tmp_disk_tables server executes statements
The number of temporary files that Created_tmp_files mysqld has created
The number of temporary tables in memory automatically created by the Created_tmp_tables server when the statement is executed. If the Created_tmp_disk_tables is large, you may want to increase the tmp_table_ size value to make temporary tables memory-based rather than hard disk-based.
The number of lines with errors written by Delayed_errors in INSERT DELAYED (possibly duplicate key).
The number of INSERT DELAYED processor threads used by Delayed_insert_threads Global.
Number of INSERT DELAYED rows written by Delayed_writes
The number of FLUSH statements executed by Flush_commands.
Number of statements submitted within Handler_commit
The number of times the Handler_delete row was deleted from the table.
The Handler_discover MySQL server can ask the NDB CLUSTER storage engine if it knows a table with a certain name. It's called discovery. Handler_discover indicates the number of times it has been discovered by this method.
Handler_prepare A counter for the prepare phase of two-phase commit operations.
The number of times the first item in the Handler_read_first index was read. If high, it recommends that the server is performing a large number of full index scans; for example, SELECT col1 FROM foo, assume that col1 has an index.
The number of requests for Handler_read_key to read a row based on the key. If high, the query and table are indexed correctly.
Handler_read_next reads the number of requests for the next row in key order. If you use a range constraint or if you perform an index scan to query the index column, this value is increased.
Handler_read_prev reads the number of requests for the previous line in key order. This reading method is mainly used to optimize ORDER BY. DESC .
The number of requests for Handler_read_rnd to read a line based on a fixed location. This value is higher if you are executing a large number of queries and need to sort the results. You may use a large number of queries that require MySQL to scan the entire table or your connection does not use keys correctly.
The number of requests for Handler_read_rnd_next to read the next line in the data file. If you are doing a lot of table scans, the value is higher. It usually indicates that your table index is incorrect or that the query you write does not make use of the index.
The number of ROLLBACK statements within the Handler_rollback.
The number of requests that Handler_savepoint places a SavePoint in a storage engine.
Handler_savepoint_rollback is required in a storage engine to roll back to a number of save points.
The number of requests for Handler_update to update a row in the table.
The number of requests for Handler_write to insert a row in the table.
The number of pages (dirty or clean) that the Innodb_buffer_pool_pages_data contains data.
The current number of dirty pages in Innodb_buffer_pool_pages_dirty.
Number of buffer pool pages required by Innodb_buffer_pool_pages_flushed Global to be emptied
The number of empty pages in Innodb_buffer_pool_pages_free.
The number of pages locked by Innodb_buffer_pool_pages_latched Global in the InnoDB buffer pool. This is the number of pages that are currently being read or written or cannot be emptied or deleted for other reasons.
The number of Innodb_buffer_pool_pages_misc busy pages because they have been assigned priority for management, such as row locking or applicable hash indexes. This value can also be calculated as Innodb_buffer_pool_pages_total-Innodb_buffer_pool_pages_free-Innodb_buffer_pool_pages_data.
Total Innodb_buffer_pool_pages_total buffer pool size (number of pages).
The number of "random" read-aheads initialized by Innodb_buffer_pool_read_ahead_rnd Global InnoDB. Occurs when a query scans a large portion of a table in random order.
The number of sequential read-aheads initialized by Innodb_buffer_pool_read_ahead_seq Global InnoDB. Occurs when InnoDB performs a sequential full table scan.
The number of logical read requests completed by Innodb_buffer_pool_read_requests Global InnoDB.
Innodb_buffer_pool_reads cannot satisfy the number of logical reads in the buffer pool that InnoDB must read per page.
Innodb_buffer_pool_wait_free generally writes to the InnoDB buffer pool through the background. However, if you need to read or create a page, and there is no clean page available, it also needs to wait for the page to be empty. This counter counts the waiting instances. This value should be small if the buffer pool size has been set appropriately.
The number of writes from Innodb_buffer_pool_write_requests to the InnoDB buffer pool.
The Innodb_data_fsyncs fsync () Operand.
The currently pending fsync () Operand of Innodb_data_pending_fsyncs.
Innodb_data_pending_reads 's currently pending readings.
The number of writes currently pending by Innodb_data_pending_writes.
The number of data (in bytes) that Innodb_data_read has read so far.
Total number of Innodb_data_reads data reads.
Total number of Innodb_data_writes data writes.
The amount of data (in bytes) that Innodb_data_written has written so far.
Number of double write operations performed by Innodb_dblwr_pages_written
The number of pages that have been written by Innodb_dblwr_writes double write operation
The amount of time that Innodb_log_waits must wait because the log buffer is too small and we must wait for it to be emptied before continuing
The number of Innodb_log_write_requests log write requests.
The number of physical writes Innodb_log_writes made to the log file.
The number of fsync () writes completed by Innodb_os_log_fsyncs to the log file.
The number of Innodb_os_log_pending_fsyncs pending log file fsync () operations.
Innodb_os_log_pending_writes pending log file write operation
The number of bytes Innodb_os_log_written wrote to the log file.
The InnoDB page size compiled by Innodb_page_size (the default 16KB). Many values are counted in pages; the size of the page is easily converted to bytes.
The number of pages created by Innodb_pages_created.
The number of pages read by Innodb_pages_read.
The number of pages written by Innodb_pages_written.
The number of rows that Innodb_row_lock_current_waits is currently waiting to lock.
The total time, in milliseconds, spent on Innodb_row_lock_time row locking.
The average time in milliseconds that an Innodb_row_lock_time_avg row is locked.
The maximum time in milliseconds that an Innodb_row_lock_time_max row is locked.
The number of times a row of Innodb_row_lock_waits locks must wait.
The number of rows deleted by Innodb_rows_deleted from the InnoDB table.
The number of rows that Innodb_rows_inserted inserts into the InnoDB table.
The number of rows read by Innodb_rows_read from the InnoDB table.
The number of rows updated in the Innodb_rows_updated InnoDB table.
The number of blocks in the Key_blocks_not_flushed key cache that have changed but have not been emptied to the hard disk.
The number of unused blocks in the Key_blocks_unused key cache. You can use this value to determine how many key caches are used
The number of blocks used in the Key_blocks_used Global key cache. This value is a high horizontal mark indicating how many blocks have been used at the same time.
The number of requests for data blocks that Key_read_requests read keys from the cache.
The number of times Key_reads reads blocks of keys from the hard disk. If the Key_reads is large, the Key_buffer_ size value may be too small. You can use Key_reads/Key_read_requests to calculate the cache loss rate.
The number of requests that Key_write_requests wrote blocks of key to the cache.
The number of times Key_writes writes to the hard disk the physical write operation of the block of data that will be the key.
The total cost of the last compiled query calculated by Last_query_cost Session using the query optimizer. Used to compare the costs of different query schemes for the same query. The default value of 0 means that the query has not been compiled. The default value is 0. Last_query_cost has session scope.
The maximum number of connections that have been used simultaneously since the Max_used_connections server was started.
The number of rows that Not_flushed_delayed_rows is waiting to write to the INSERT DELAY queue.
The number of files opened by Open_files.
The number of streams opened by Open_streams (mainly for recording).
Number of .frm files cached by Open_table_definitions
The number of tables currently open by Open_tables.
Number of Opened_files Global file openings. Files of other types such as sockets or pipes are not included. It also does not include files that the storage engine uses to do its own internal functions.
Number of .frm files cached by Opened_table_definitions
The number of tables that Opened_tables has opened. If the Opened_tables is large, the table_cache value may be too small.
The current number of preprocessing statements for Prepared_stmt_count. (maximum number is system variable: max_prepared_stmt_count)
The number of free memory blocks in the Qcache_free_blocks query cache.
The amount of free memory used by Qcache_free_memory to query the cache.
The number of times the Qcache_hits Global query cache was accessed.
The number of queries that Qcache_inserts Global added to the cache.
The number of queries deleted from the cache by Qcache_lowmem_prunes due to low memory.
The number of Qcache_not_cached non-cached queries (not cacheable, or because the query_cache_type setting is not cached).
The number of queries that Qcache_queries_in_cache enlisted in the cache.
The total number of blocks in the Qcache_total_blocks query cache.
The number of requests executed by the Queries server, including requests in the stored procedure.
The number of queries that Questions has sent to the server.
Rpl_status Global failed secure replication status (not yet in use).
The number of joins that Select_full_join does not use indexes. If the value is not 0, you should check the index of the table carefully
The number of joins that Select_full_range_join searches for using ranges in referenced tables.
The number of joins in which Select_range uses ranges in the first table. The general situation is not a critical issue, even if the value is quite large.
The number of joins without key values checked by Select_range_check after each row of data. If not 0, you should check the index of the table carefully.
The number of joins that Select_scan fully scanned the first table.
Heartbeat interval for Slave_heartbeat_period replication
Number of temporary tables opened by Slave_open_temp_tables from the server
Number of heartbeats from Slave_received_heartbeats slave server
Number of Slave_retried_transactions replication thread retries from the server since this startup
Slave_running this value is ON if the server is a slave server connected to the master server.
The number of threads whose Slow_launch_threads creation time exceeds slow_launch_time seconds.
The number of queries whose Slow_queries query time exceeds long_query_time seconds.
The number of mergers that have been performed by the Sort_merge_passes sorting algorithm. If the value of this variable is large, consider increasing the value of the sort_buffer_size system variable.
The number of sorts performed by Sort_range in the range.
The number of rows that Sort_rows has sorted.
The number of sorts completed by the Sort_scan by scanning the table.
Ssl_* ssl connection related
The number of locks on the table that Table_locks_immediate immediately acquired.
The number of locks on the table that Table_locks_waited could not immediately acquire. If the value is high and there is a performance problem, you should first optimize the query, and then split the table or use replication.
The number of threads in the Threads_cached thread cache.
The number of connections currently open by Threads_connected.
The number of threads created by Threads_created to process connections. If the Threads_created is large, you may want to increase the thread_cache_ size value. The cache access rate is calculated by Threads_created/Connections.
The number of (non-sleeping) threads activated by Threads_running.
The time in seconds that the Uptime server has been running.
The time in seconds that Uptime_since_flush_status last used FLUSH STATUS.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.