Aborted_clients Aborted_clients

由于客户端在未正确关闭连接的情况下终止，导致的连接中断次数。参见 B.3.2.9 节，“通信错误和中止连接”。The number of connections that were aborted because the client died without closing the connection properly. See Section B.3.2.9, “Communication Errors and Aborted Connections”.

Aborted_connects Aborted_connects

尝试连接到 MySQL 服务器失败的次数。参见 B.3.2.9 节，“通信错误和中止连接”。The number of failed attempts to connect to the MySQL server. See Section B.3.2.9, “Communication Errors and Aborted Connections”.

有关更多连接相关的信息，请查看 Connection_errors_xxx 状态变量以及 host_cache 表。For additional connection-related information, check the Connection_errors_xxx status variables and the host_cache table.

Authentication_ldap_sasl_supported_methods Authentication_ldap_sasl_supported_methods

实现 SASL LDAP 身份验证的 authentication_ldap_sasl 插件支持多种身份验证方法，但根据主机系统配置，它们可能并非全部可用。Authentication_ldap_sasl_supported_methods 变量提供对支持方法的可发现性。其值是由空格分隔的支持方法名称组成的字符串。例如："SCRAM-SHA 1 SCRAM-SHA-256 GSSAPI"The authentication_ldap_sasl plugin that implements SASL LDAP authentication supports multiple authentication methods, but depending on host system configuration, they might not all be available. The Authentication_ldap_sasl_supported_methods variable provides discoverability for the supported methods. Its value is a string consisting of supported method names separated by spaces. Example: "SCRAM-SHA 1 SCRAM-SHA-256 GSSAPI"

Binlog_cache_disk_use Binlog_cache_disk_use

使用临时二进制日志缓存但超过binlog_cache_size的值，并使用临时文件存储事务中的语句的事务数量。The number of transactions that used the temporary binary log cache but that exceeded the value of binlog_cache_size and used a temporary file to store statements from the transaction.

非事务性语句导致二进制日志事务缓存写入磁盘的次数在Binlog_stmt_cache_disk_use状态变量中单独跟踪。The number of nontransactional statements that caused the binary log transaction cache to be written to disk is tracked separately in the Binlog_stmt_cache_disk_use status variable.

Acl_cache_items_count Acl_cache_items_count

缓存的权限对象数量。每个对象都是用户及其激活角色的权限组合。The number of cached privilege objects. Each object is the privilege combination of a user and its active roles.

Binlog_cache_use Binlog_cache_use

使用二进制日志缓存的事务数量。The number of transactions that used the binary log cache.

Binlog_stmt_cache_disk_use

使用二进制日志语句缓存的非事务语句数量，但超过了 binlog_stmt_cache_size 的值，并使用临时文件来存储这些语句。The number of nontransaction statements that used the binary log statement cache but that exceeded the value of binlog_stmt_cache_size and used a temporary file to store those statements.

Binlog_stmt_cache_use

使用二进制日志语句缓存的非事务性语句数量。The number of nontransactional statements that used the binary log statement cache.

Bytes_received Bytes_received

从所有客户端接收到的字节数。The number of bytes received from all clients.

Bytes_sent Bytes_sent

发送给所有客户端的字节数。The number of bytes sent to all clients.

Caching_sha2_password_rsa_public_key Caching_sha2_password_rsa_public_key

由 caching_sha2_password 认证插件使用的公钥，用于基于 RSA 密钥对的密码交换。只有在服务器成功初始化由 caching_sha2_password_private_key_path 和 caching_sha2_password_public_key_path 系统变量指定的文件中的私钥和公钥时，该值才非空。Caching_sha2_password_rsa_public_key 的值来自后者的文件。The public key used by the caching_sha2_password authentication plugin for RSA key pair-based password exchange. The value is nonempty only if the server successfully initializes the private and public keys in the files named by the caching_sha2_password_private_key_path and caching_sha2_password_public_key_path system variables. The value of Caching_sha2_password_rsa_public_key comes from the latter file.

Com_xxx

Com_xxx 语句计数器变量表示每个 xxx 语句已执行的次数。每种类型的语句都有一个状态变量。例如，Com_delete 和 Com_update 分别统计 DELETE 和 UPDATE 语句的次数。Com_delete_multi 和 Com_update_multi 类似，但适用于使用多表语法的 DELETE 和 UPDATE 语句。The Com_xxx statement counter variables indicate the number of times each xxx statement has been executed. There is one status variable for each type of statement. For example, Com_delete and Com_update count DELETE and UPDATE statements, respectively. Com_delete_multi and Com_update_multi are similar but apply to DELETE and UPDATE statements that use multiple-table syntax.

即使预处理语句的参数未知或执行过程中发生错误，所有 Com_stmt_xxx 变量也会增加。换句话说，它们的值对应的是发出的请求数量，而不是成功完成的请求数量。例如，由于状态变量在每次服务器启动时初始化，并且不会在重启后保留，因此用于跟踪 RESTART 和 SHUTDOWN 语句的 Com_restart 和 Com_shutdown 变量通常为零，但如果执行了 RESTART 或 SHUTDOWN 但失败，这些变量可能会非零。All Com_stmt_xxx variables are increased even if a prepared statement argument is unknown or an error occurred during execution. In other words, their values correspond to the number of requests issued, not to the number of requests successfully completed. For example, because status variables are initialized for each server startup and do not persist across restarts, the Com_restart and Com_shutdown variables that track RESTART and SHUTDOWN statements normally have a value of zero, but can be nonzero if RESTART or SHUTDOWN statements were executed but failed.

Com_stmt_xxx 状态变量如下：The Com_stmt_xxx status variables are as follows:

这些变量代表预处理语句命令。它们的名称指代网络层中使用的 COM_xxx 命令集。换句话说，每当执行诸如 mysql_stmt_prepare()、mysql_stmt_execute() 等预处理语句 API 调用时，它们的值会增加。然而，Com_stmt_prepare、Com_stmt_execute 和 Com_stmt_close 也会分别因 PREPARE、EXECUTE 或 DEALLOCATE PREPARE 而增加。此外，较旧的语句计数器变量 Com_prepare_sql、Com_execute_sql 和 Com_dealloc_sql 在执行 PREPARE、EXECUTE 和 DEALLOCATE PREPARE 语句时会增加。Com_stmt_fetch 表示从游标获取数据时发出的网络往返总次数。Those variables stand for prepared statement commands. Their names refer to the COM_xxx command set used in the network layer. In other words, their values increase whenever prepared statement API calls such as mysql_stmt_prepare(), mysql_stmt_execute(), and so forth are executed. However, Com_stmt_prepare, Com_stmt_execute and Com_stmt_close also increase for PREPARE, EXECUTE, or DEALLOCATE PREPARE, respectively. Additionally, the values of the older statement counter variables Com_prepare_sql, Com_execute_sql, and Com_dealloc_sql increase for the PREPARE, EXECUTE, and DEALLOCATE PREPARE statements. Com_stmt_fetch stands for the total number of network round-trips issued when fetching from cursors.

Com_stmt_reprepare 表示语句被服务器自动重新准备的次数，例如在语句引用的表或视图的元数据发生变化后。重新准备操作会增加 Com_stmt_reprepare，同时也会增加 Com_stmt_prepare。Com_stmt_reprepare indicates the number of times statements were automatically reprepared by the server, for example, after metadata changes to tables or views referred to by the statement. A reprepare operation increments Com_stmt_reprepare, and also Com_stmt_prepare.

Com_explain_other 表示执行的 EXPLAIN FOR CONNECTION 语句的次数。详见 第 10.8.4 节，“获取指定连接的执行计划信息”。Com_explain_other indicates the number of EXPLAIN FOR CONNECTION statements executed. See Section 10.8.4, “Obtaining Execution Plan Information for a Named Connection”.

Com_change_repl_filter 表示执行的 CHANGE REPLICATION FILTER 语句的数量。Com_change_repl_filter indicates the number of CHANGE REPLICATION FILTER statements executed.

Compression Compression

客户端连接在客户端/服务器协议中是否使用压缩。Whether the client connection uses compression in the client/server protocol.

此状态变量已被弃用；预计将在 MySQL 的未来版本中移除。请参阅 配置遗留连接压缩。This status variable is deprecated; expect it to be removed in a future version of MySQL. See Configuring Legacy Connection Compression.

Compression_algorithm Compression_algorithm

用于当前与服务器连接的压缩算法的名称。该值可以是 protocol_compression_algorithms 系统变量允许的任何算法。例如，如果连接未使用压缩，则该值为 uncompressed；如果连接使用 zlib 算法，则该值为 zlib。The name of the compression algorithm in use for the current connection to the server. The value can be any algorithm permitted in the value of the protocol_compression_algorithms system variable. For example, the value is uncompressed if the connection does not use compression, or zlib if the connection uses the zlib algorithm.

更多信息，请参阅 第 6.2.8 节，“连接压缩控制”。For more information, see Section 6.2.8, “Connection Compression Control”.

Compression_level Compression_level

当前连接到服务器使用的压缩级别。对于 zlib 连接（默认的 zlib 算法压缩级别），该值为 6；对于 zstd 连接，该值为 1 到 22；对于 uncompressed 连接，该值为 0。The compression level in use for the current connection to the server. The value is 6 for zlib connections (the default zlib algorithm compression level), 1 to 22 for zstd connections, and 0 for uncompressed connections.

更多信息，请参阅 第 6.2.8 节，“连接压缩控制”。For more information, see Section 6.2.8, “Connection Compression Control”.

Connection_errors_xxx Connection_errors_xxx

这些变量提供有关客户端连接过程中发生的错误的信息。它们仅为全局变量，表示从所有主机的连接汇总的错误计数。这些变量跟踪主机缓存未计入的错误（参见第 7.1.12.3 节，“DNS 查找和主机缓存”），例如未与 TCP 连接相关的错误、连接过程非常早期（甚至在知道 IP 地址之前）发生的错误，或不针对任何特定 IP 地址的错误（例如内存不足情况）。These variables provide information about errors that occur during the client connection process. They are global only and represent error counts aggregated across connections from all hosts. These variables track errors not accounted for by the host cache (see Section 7.1.12.3, “DNS Lookups and the Host Cache”), such as errors that are not associated with TCP connections, occur very early in the connection process (even before an IP address is known), or are not specific to any particular IP address (such as out-of-memory conditions).

Connections Connections

对 MySQL 服务器的连接尝试次数（无论是否成功）。The number of connection attempts (successful or not) to the MySQL server.

Created_tmp_disk_tables Created_tmp_disk_tables

服务器在执行语句时创建的内部磁盘临时表的数量。The number of internal on-disk temporary tables created by the server while executing statements.

您可以通过比较 Created_tmp_disk_tables 和 Created_tmp_tables 的数值，来比较创建的内部磁盘临时表数量与创建的内部临时表总数。You can compare the number of internal on-disk temporary tables created to the total number of internal temporary tables created by comparing Created_tmp_disk_tables and Created_tmp_tables values.

另请参见 第 10.4.4 节，“MySQL 中的内部临时表使用”。See also Section 10.4.4, “Internal Temporary Table Use in MySQL”.

Created_tmp_files Created_tmp_files

mysqld创建了多少临时文件。How many temporary files mysqld has created.

Created_tmp_tables Created_tmp_tables

服务器在执行语句时创建的内部临时表的数量。The number of internal temporary tables created by the server while executing statements.

您可以通过比较 Created_tmp_disk_tables 和 Created_tmp_tables 的数值，来比较创建的内部磁盘临时表数量与创建的内部临时表总数。You can compare the number of internal on-disk temporary tables created to the total number of internal temporary tables created by comparing Created_tmp_disk_tables and Created_tmp_tables values.

另请参见 第 10.4.4 节，“MySQL 中的内部临时表使用”。See also Section 10.4.4, “Internal Temporary Table Use in MySQL”.

每次调用 SHOW STATUS 语句时，都会使用一个内部临时表，并增加全局 Created_tmp_tables 值。Each invocation of the SHOW STATUS statement uses an internal temporary table and increments the global Created_tmp_tables value.

Current_tls_ca Current_tls_ca

服务器用于新连接的 SSL 上下文中活动的 ssl_ca 值。如果系统变量已更改，但尚未执行 ALTER INSTANCE RELOAD TLS 来根据上下文相关的系统变量值重新配置 SSL 上下文并更新相应的状态变量，则该上下文值可能与当前的 ssl_ca 系统变量值不同。（这种值的潜在差异适用于每一对相应的上下文相关系统变量和状态变量。参见 加密连接的服务器端运行时配置与监控。）The active ssl_ca value in the SSL context that the server uses for new connections. This context value may differ from the current ssl_ca system variable value if the system variable has been changed but ALTER INSTANCE RELOAD TLS has not subsequently been executed to reconfigure the SSL context from the context-related system variable values and update the corresponding status variables. (This potential difference in values applies to each corresponding pair of context-related system and status variables. See Server-Side Runtime Configuration and Monitoring for Encrypted Connections.)

Current_tls_xxx 状态变量的值也可以通过性能模式 tls_channel_status 表获得。请参阅 第 29.12.22.9 节，“tls_channel_status 表”。The Current_tls_xxx status variable values are also available through the Performance Schema tls_channel_status table. See Section 29.12.22.9, “The tls_channel_status Table”.

Current_tls_capath Current_tls_capath

服务器用于新连接的 TLS 上下文中活动的 ssl_capath 值。有关此状态变量与其对应系统变量之间关系的说明，请参阅 Current_tls_ca 的描述。The active ssl_capath value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_cert Current_tls_cert

服务器用于新连接的 TLS 上下文中的活动 ssl_cert 值。有关此状态变量与其对应的系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active ssl_cert value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_cipher Current_tls_cipher

服务器用于新连接的 TLS 上下文中的活动 ssl_cipher 值。有关此状态变量与其对应的系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active ssl_cipher value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_ciphersuites Current_tls_ciphersuites

服务器用于新连接的 TLS 上下文中的活动 tls_ciphersuites 值。关于此状态变量与其对应的系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active tls_ciphersuites value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_crl Current_tls_crl

服务器在新连接中使用的 TLS 上下文中活动的 ssl_crl 值。有关此状态变量与其相应系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active ssl_crl value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_crlpath

服务器用于新连接的 TLS 上下文中活动的 ssl_crlpath 值。有关此状态变量与其对应系统变量之间关系的说明，请参阅 Current_tls_ca 的描述。The active ssl_crlpath value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_key

服务器用于新连接的 TLS 上下文中的活动 ssl_key 值。有关此状态变量与其对应的系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active ssl_key value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Current_tls_version

服务器用于新连接的 TLS 上下文中的活动 tls_version 值。关于此状态变量与其对应系统变量之间关系的说明，请参见 Current_tls_ca 的描述。The active tls_version value in the TLS context that the server uses for new connections. For notes about the relationship between this status variable and its corresponding system variable, see the description of Current_tls_ca.

Delayed_errors

此状态变量已被弃用（因为不支持 DELAYED 插入）；预计将在未来版本中移除。This status variable is deprecated (because DELAYED inserts are not supported); expect it to be removed in a future release.

Delayed_insert_threads

此状态变量已被弃用（因为不支持 DELAYED 插入）；预计将在未来版本中移除。This status variable is deprecated (because DELAYED inserts are not supported); expect it to be removed in a future release.

Delayed_writes Delayed_writes

此状态变量已被弃用（因为不支持 DELAYED 插入）；预计将在未来版本中移除。This status variable is deprecated (because DELAYED inserts are not supported); expect it to be removed in a future release.

Deprecated_use_i_s_processlist_count Deprecated_use_i_s_processlist_count

自上次重启以来，访问 information_schema.processlist 表的次数。How many times the information_schema.processlist table has been accessed since the last restart.

Deprecated_use_i_s_processlist_last_timestamp Deprecated_use_i_s_processlist_last_timestamp

自上次重启以来，指示最后一次访问 information_schema.processlist 表的时间戳。显示自 Unix 纪元以来的微秒数。A timestamp indicating the last time the information_schema.processlist table has been accessed since the last restart. Shows microseconds since the Unix Epoch.

dragnet.Status

最近一次对 dragnet.log_error_filter_rules 系统变量的赋值结果，如果没有发生过赋值则为空。The result of the most recent assignment to the dragnet.log_error_filter_rules system variable, empty if no such assignment has occurred.

Error_log_buffered_bytes Error_log_buffered_bytes

Performance Schema error_log 表当前使用的字节数。这个值有可能会减少，例如，如果新事件无法适应，必须丢弃旧事件，但新事件比旧事件小。The number of bytes currently used in the Performance Schema error_log table. It is possible for the value to decrease, for example, if a new event cannot fit until discarding an old event, but the new event is smaller than the old one.

Error_log_buffered_events Error_log_buffered_events

当前存在于性能模式 error_log 表中的事件数量。与 Error_log_buffered_bytes 一样，值可能会减少。The number of events currently present in the Performance Schema error_log table. As with Error_log_buffered_bytes, it is possible for the value to decrease.

Error_log_expired_events Error_log_expired_events

从性能模式 error_log 表中丢弃的事件数量，以为新事件腾出空间。The number of events discarded from the Performance Schema error_log table to make room for new events.

Error_log_latest_write Error_log_latest_write

最后一次写入 Performance Schema error_log 表的时间。The time of the last write to the Performance Schema error_log table.

Flush_commands

服务器刷新表的次数，无论是因为用户执行了FLUSH TABLES语句，还是由于内部服务器操作引起的。收到COM_REFRESH数据包时，也会增加此计数。这与Com_flush不同，后者表示已经执行了多少个FLUSH语句，无论是FLUSH TABLES，FLUSH LOGS，等等。The number of times the server flushes tables, whether because a user executed a FLUSH TABLES statement or due to internal server operation. It is also incremented by receipt of a COM_REFRESH packet. This is in contrast to Com_flush, which indicates how many FLUSH statements have been executed, whether FLUSH TABLES, FLUSH LOGS, and so forth.

Global_connection_memory

所有用户连接到服务器所使用的内存。系统线程或 MySQL 根账户使用的内存也包含在总量内，但这些线程或用户不会因内存使用而被断开连接。除非启用了 global_connection_memory_tracking（默认禁用），否则不会计算此内存。性能模式也必须启用。The memory used by all user connections to the server. Memory used by system threads or by the MySQL root account is included in the total, but such threads or users are not subject to disconnection due to memory usage. This memory is not calculated unless global_connection_memory_tracking is enabled (disabled by default). The Performance Schema must also be enabled.

您可以通过设置 connection_memory_chunk_size（间接地）控制此变量更新的频率。You can control (indirectly) the frequency with which this variable is updated by setting connection_memory_chunk_size.

Handler_commit

内部 COMMIT 语句的数量。The number of internal COMMIT statements.

Handler_delete

从表中删除行的次数。The number of times that rows have been deleted from tables.

Handler_external_lock

服务器在每次调用其 external_lock() 函数时都会增加该变量，该函数通常在访问表实例的开始和结束时调用。不同的存储引擎可能有所不同。例如，可以使用此变量来发现访问分区表的语句在加锁之前修剪了多少分区：检查该语句的计数器增加了多少，减去 2（表本身的 2 次调用），然后除以 2 就能得到被锁定的分区数。The server increments this variable for each call to its external_lock() function, which generally occurs at the beginning and end of access to a table instance. There might be differences among storage engines. This variable can be used, for example, to discover for a statement that accesses a partitioned table how many partitions were pruned before locking occurred: Check how much the counter increased for the statement, subtract 2 (2 calls for the table itself), then divide by 2 to get the number of partitions locked.

Handler_mrr_init

服务器使用存储引擎自身的多范围读取实现进行表访问的次数。The number of times the server uses a storage engine's own Multi-Range Read implementation for table access.

Handler_prepare

用于两阶段提交操作准备阶段的计数器。A counter for the prepare phase of two-phase commit operations.

Handler_read_first

索引中首次条目的读取次数。如果该值较高，则表明服务器正在执行大量全索引扫描（例如，SELECT col1 FROM foo，假设col1已建索引）。The number of times the first entry in an index was read. If this value is high, it suggests that the server is doing a lot of full index scans (for example, SELECT col1 FROM foo, assuming that col1 is indexed).

Handler_read_key

基于键读取行的请求数量。如果该值很高，这说明您的表格已经针对查询进行了适当的索引。The number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.

Handler_read_last

读取索引中最后一个键的请求次数。使用ORDER BY时，服务器会先发送一个首键请求，然后发送多个下一个键请求；而使用ORDER BY DESC时，服务器会先发送一个末键请求，然后发送多个上一个键请求。The number of requests to read the last key in an index. With ORDER BY, the server issues a first-key request followed by several next-key requests, whereas with ORDER BY DESC, the server issues a last-key request followed by several previous-key requests.

Handler_read_next

按键顺序读取下一行的请求次数。如果您在查询具有范围约束的索引列，或者正在进行索引扫描，则此值会增加。The number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.

Handler_read_prev

按键顺序读取前一行的请求次数。这种读取方法主要用于优化 ORDER BY ... DESC。The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY ... DESC.

Handler_read_rnd

基于固定位置读取行的请求数量。如果您执行大量需要对结果进行排序的查询，该值会很高。您可能有许多查询需要 MySQL 扫描整个表，或者有未正确使用键的连接。The number of requests to read a row based on a fixed position. This value is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that do not use keys properly.

Handler_read_rnd_next

读取数据文件中下一行的请求次数。如果您进行大量表扫描，该值会很高。通常，这表明您的表没有正确建立索引，或者您的查询没有编写为利用已有的索引。The number of requests to read the next row in the data file. This value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.

Handler_rollback

请求存储引擎执行回滚操作的次数。The number of requests for a storage engine to perform a rollback operation.

Handler_savepoint

请求存储引擎设置保存点的次数。The number of requests for a storage engine to place a savepoint.

Handler_savepoint_rollback

存储引擎回滚到保存点的请求次数。The number of requests for a storage engine to roll back to a savepoint.

Handler_update

更新表中某一行的请求数量。The number of requests to update a row in a table.

Handler_write Handler_write

向表中插入一行的请求数量。The number of requests to insert a row in a table.

Innodb_buffer_pool_dump_status

记录 InnoDB 缓冲池 中持有的 页面 的操作进度，该操作由设置 innodb_buffer_pool_dump_at_shutdown 或 innodb_buffer_pool_dump_now 触发。The progress of an operation to record the pages held in the InnoDB buffer pool, triggered by the setting of innodb_buffer_pool_dump_at_shutdown or innodb_buffer_pool_dump_now.

有关相关信息和示例，请参见 第 17.8.3.6 节，“保存和恢复缓冲池状态”。For related information and examples, see Section 17.8.3.6, “Saving and Restoring the Buffer Pool State”.

Innodb_buffer_pool_load_status Innodb_buffer_pool_load_status

通过读取一组对应于之前时间点的页面来热身InnoDB 缓冲池操作的进度，由设置innodb_buffer_pool_load_at_startup或innodb_buffer_pool_load_now触发。如果该操作引入过多开销，可以通过设置innodb_buffer_pool_load_abort来取消它。The progress of an operation to warm up the InnoDB buffer pool by reading in a set of pages corresponding to an earlier point in time, triggered by the setting of innodb_buffer_pool_load_at_startup or innodb_buffer_pool_load_now. If the operation introduces too much overhead, you can cancel it by setting innodb_buffer_pool_load_abort.

有关相关信息和示例，请参见 第 17.8.3.6 节，“保存和恢复缓冲池状态”。For related information and examples, see Section 17.8.3.6, “Saving and Restoring the Buffer Pool State”.

Innodb_buffer_pool_bytes_data Innodb_buffer_pool_bytes_data

InnoDB 缓冲池 中包含数据的字节总数。该数字包括脏页和干净页。对于比Innodb_buffer_pool_pages_data更准确的内存使用计算，当压缩表导致缓冲池包含不同大小的页时。The total number of bytes in the InnoDB buffer pool containing data. The number includes both dirty and clean pages. For more accurate memory usage calculations than with Innodb_buffer_pool_pages_data, when compressed tables cause the buffer pool to hold pages of different sizes.

Innodb_buffer_pool_pages_data Innodb_buffer_pool_pages_data

InnoDB 缓冲池 中包含数据的 页 数量。该数量包括 脏页 和干净页。当使用 压缩表 时，报告的 Innodb_buffer_pool_pages_data 值可能大于 Innodb_buffer_pool_pages_total（错误 #59550）。The number of pages in the InnoDB buffer pool containing data. The number includes both dirty and clean pages. When using compressed tables, the reported Innodb_buffer_pool_pages_data value may be larger than Innodb_buffer_pool_pages_total (Bug #59550).

Innodb_buffer_pool_bytes_dirty Innodb_buffer_pool_bytes_dirty

当前 InnoDB 缓冲池 中 脏页 持有的总字节数。相比 Innodb_buffer_pool_pages_dirty，在 压缩 表导致缓冲池持有不同大小的页时，更适用于更准确的内存使用计算。The total current number of bytes held in dirty pages in the InnoDB buffer pool. For more accurate memory usage calculations than with Innodb_buffer_pool_pages_dirty, when compressed tables cause the buffer pool to hold pages of different sizes.

Innodb_buffer_pool_pages_dirty Innodb_buffer_pool_pages_dirty

InnoDB 缓冲池中当前的脏页数量。The current number of dirty pages in the InnoDB buffer pool.

Innodb_buffer_pool_pages_flushed Innodb_buffer_pool_pages_flushed

请求将 InnoDB 缓冲池 中的 页 刷新 的次数。The number of requests to flush pages from the InnoDB buffer pool.

Innodb_buffer_pool_pages_free Innodb_buffer_pool_pages_free

InnoDB 缓冲池 中空闲 页 的数量。The number of free pages in the InnoDB buffer pool.

Innodb_buffer_pool_pages_latched Innodb_buffer_pool_pages_latched

InnoDB 缓冲池 中已锁定的 页 的数量。这些页面当前正在被读取或写入，或者由于某些其他原因无法被 刷新 或移除。计算此变量开销较大，因此仅在服务器构建时定义了 UNIV_DEBUG 系统时可用。The number of latched pages in the InnoDB buffer pool. These are pages currently being read or written, or that cannot be flushed or removed for some other reason. Calculation of this variable is expensive, so it is available only when the UNIV_DEBUG system is defined at server build time.

Innodb_buffer_pool_pages_misc

InnoDB 缓冲池中因分配给管理开销（例如行锁或自适应哈希索引）而被占用的页数。此值也可以通过计算 Innodb_buffer_pool_pages_total − Innodb_buffer_pool_pages_free − Innodb_buffer_pool_pages_data 得出。当使用压缩表时，Innodb_buffer_pool_pages_misc可能会报告超出范围的值（Bug #59550）。The number of pages in the InnoDB buffer pool that are busy because they have been allocated for administrative overhead, such as row locks or the adaptive hash index. This value can also be calculated as Innodb_buffer_pool_pages_total − Innodb_buffer_pool_pages_free − Innodb_buffer_pool_pages_data. When using compressed tables, Innodb_buffer_pool_pages_misc may report an out-of-bounds value (Bug #59550).

Innodb_buffer_pool_pages_total Innodb_buffer_pool_pages_total

InnoDB 缓冲池 的总大小，以 页 为单位。当使用 压缩表 时，报告的 Innodb_buffer_pool_pages_data 值可能大于 Innodb_buffer_pool_pages_total（Bug #59550）The total size of the InnoDB buffer pool, in pages. When using compressed tables, the reported Innodb_buffer_pool_pages_data value may be larger than Innodb_buffer_pool_pages_total (Bug #59550)

Innodb_buffer_pool_read_ahead Innodb_buffer_pool_read_ahead

由预读后台线程读取到InnoDB 缓冲池中的页面数量。The number of pages read into the InnoDB buffer pool by the read-ahead background thread.

Innodb_buffer_pool_read_ahead_evicted Innodb_buffer_pool_read_ahead_evicted

由预读后台线程读取到InnoDB 缓冲池中但随后被逐出而未被查询访问的页数 without having been accessed by queries.The number of pages read into the InnoDB buffer pool by the read-ahead background thread that were subsequently evicted without having been accessed by queries.

Innodb_buffer_pool_read_ahead_rnd Innodb_buffer_pool_read_ahead_rnd

由“随机”由...发起的预读InnoDB。当查询以随机顺序扫描表的大部分数据时会发生这种情况。The number of “random” read-aheads initiated by InnoDB. This happens when a query scans a large portion of a table but in random order.

Innodb_buffer_pool_read_requests

逻辑读取请求的数量。The number of logical read requests.

Innodb_buffer_pool_reads

无法从InnoDB满足的逻辑读取次数，只能直接从磁盘读取。缓冲池尝试连接被锁定用户帐户的次数。有关帐户锁定和解锁的信息，请参见The number of logical reads that InnoDB could not satisfy from the buffer pool, and had to read directly from disk.

Innodb_buffer_pool_resize_status

通过动态设置 innodb_buffer_pool_size 参数触发的动态调整 InnoDB 缓冲池 大小的操作状态。innodb_buffer_pool_size 参数是动态的，这允许您在不重启服务器的情况下调整缓冲池大小。有关相关信息，请参见 在线配置 InnoDB 缓冲池大小。The status of an operation to resize the InnoDB buffer pool dynamically, triggered by setting the innodb_buffer_pool_size parameter dynamically. The innodb_buffer_pool_size parameter is dynamic, which allows you to resize the buffer pool without restarting the server. See Configuring InnoDB Buffer Pool Size Online for related information.

Innodb_buffer_pool_resize_status_code

报告用于跟踪在线缓冲池调整操作的状态代码。每个状态代码表示调整操作中的一个阶段。状态代码包括：Reports status codes for tracking online buffer pool resizing operations. Each status code represents a stage in a resizing operation. Status codes include:

您可以将此状态变量与 Innodb_buffer_pool_resize_status_progress 结合使用，以跟踪调整操作每个阶段的进度。Innodb_buffer_pool_resize_status_progress 变量报告一个百分比值，表示当前阶段的进度。You can use this status variable in conjunction with Innodb_buffer_pool_resize_status_progress to track the progress of each stage of a resizing operation. The Innodb_buffer_pool_resize_status_progress variable reports a percentage value indicating the progress of the current stage.

有关更多信息，请参见 监控在线缓冲池调整进度。For more information, see Monitoring Online Buffer Pool Resizing Progress.

Innodb_buffer_pool_resize_status_progress Innodb_buffer_pool_resize_status_progress

报告一个百分比值，指示在线缓冲池调整大小操作当前阶段的进度。该变量与Innodb_buffer_pool_resize_status_code一起使用，后者报告一个状态代码，指示在线缓冲池调整大小操作的当前阶段。Reports a percentage value indicating the progress of the current stage of an online buffer pool resizing operation. This variable is used in conjunction with Innodb_buffer_pool_resize_status_code, which reports a status code indicating the current stage of an online buffer pool resizing operation.

在处理每个缓冲池实例后，百分比值会更新。当状态代码（由 Innodb_buffer_pool_resize_status_code 报告）从一种状态变为另一种状态时，百分比值会重置为 0。The percentage value is updated after each buffer pool instance is processed. As the status code (reported by Innodb_buffer_pool_resize_status_code) changes from one status to another, the percentage value is reset to 0.

有关相关信息，请参见 监控在线缓冲池调整进度。For related information, see Monitoring Online Buffer Pool Resizing Progress.

Innodb_buffer_pool_wait_free Innodb_buffer_pool_wait_free

通常，对 InnoDB 缓冲池 的写入会在后台进行。当 InnoDB 需要读取或创建一个 页，但没有可用的干净页时，InnoDB 会先刷新一些 脏页 并等待该操作完成。此计数器统计这些等待的次数。如果 innodb_buffer_pool_size 设置得当，此值应该很小。Normally, writes to the InnoDB buffer pool happen in the background. When InnoDB needs to read or create a page and no clean pages are available, InnoDB flushes some dirty pages first and waits for that operation to finish. This counter counts instances of these waits. If innodb_buffer_pool_size has been set properly, this value should be small.

Innodb_buffer_pool_write_requests Innodb_buffer_pool_write_requests

对 InnoDB 缓冲池 进行的写入次数。The number of writes done to the InnoDB buffer pool.

Innodb_data_fsyncs Innodb_data_fsyncs

迄今为止的 fsync() 操作次数。fsync() 调用的频率受 innodb_flush_method 配置选项的设置影响。The number of fsync() operations so far. The frequency of fsync() calls is influenced by the setting of the innodb_flush_method configuration option.

如果启用了innodb_use_fdatasync，则统计fdatasync()操作的次数。Counts the number of fdatasync() operations if innodb_use_fdatasync is enabled.

Innodb_data_pending_fsyncs

当前待处理的fsync()操作数。fsync()调用的频率受innodb_flush_method配置选项设置的影响。The current number of pending fsync() operations. The frequency of fsync() calls is influenced by the setting of the innodb_flush_method configuration option.

Innodb_data_pending_reads

当前待处理的读取数量。The current number of pending reads.

Innodb_data_pending_writes

当前待处理写入的数量。The current number of pending writes.

Innodb_data_read

自服务器启动以来读取的数据量（以字节为单位）。The amount of data read since the server was started (in bytes).

Innodb_data_reads

数据读取的总次数（操作系统文件读取）。The total number of data reads (OS file reads).

Innodb_data_writes

数据写入的总次数。The total number of data writes.

Innodb_data_written

到目前为止写入的数据量，单位为字节。The amount of data written so far, in bytes.

Innodb_dblwr_pages_written

写入到双写缓冲区的页的数量。参见第 17.11.1 节，“InnoDB 磁盘 I/O”。The number of pages that have been written to the doublewrite buffer. See Section 17.11.1, “InnoDB Disk I/O”.

Innodb_dblwr_writes

已执行的双写操作次数。参见第 17.11.1 节，“InnoDB 磁盘 I/O”。The number of doublewrite operations that have been performed. See Section 17.11.1, “InnoDB Disk I/O”.

Innodb_have_atomic_builtins

指示服务器是否使用原子指令构建。Indicates whether the server was built with atomic instructions.

Innodb_log_waits

日志缓冲区log buffer太小，需要等待wait才能在继续之前将其flush的次数。The number of times that the log buffer was too small and a wait was required for it to be flushed before continuing.

Innodb_log_write_requests

对 InnoDB 重做日志 的写请求数量。The number of write requests for the InnoDB redo log.

Innodb_log_writes

对 InnoDB 重做日志 文件的物理写入次数。The number of physical writes to the InnoDB redo log file.

Innodb_num_open_files

InnoDB 当前打开的文件数量。The number of files InnoDB currently holds open.

Innodb_os_log_fsyncs

对 InnoDB 重做日志 文件执行的 fsync() 写入次数。The number of fsync() writes done to the InnoDB redo log files.

Innodb_os_log_pending_fsyncs

InnoDB 重做日志 文件待执行的 fsync() 操作数量。The number of pending fsync() operations for the InnoDB redo log files.

Innodb_os_log_pending_writes

等待写入InnoDB 重做日志文件的数量。The number of pending writes to the InnoDB redo log files.

Innodb_os_log_written

写入InnoDB 重做日志文件的字节数。The number of bytes written to the InnoDB redo log files.

Innodb_page_size

InnoDB 页面大小（默认 16KB）。许多值以页面为单位计算；页面大小使它们能够轻松转换为字节。InnoDB page size (default 16KB). Many values are counted in pages; the page size enables them to be easily converted to bytes.

Innodb_pages_created

操作 InnoDB 表创建的页面数。The number of pages created by operations on InnoDB tables.

Innodb_pages_read

操作 InnoDB 表时从 InnoDB 缓冲池读取的页面数。The number of pages read from the InnoDB buffer pool by operations on InnoDB tables.

Innodb_pages_written

通过对InnoDB表的操作写入的页数。The number of pages written by operations on InnoDB tables.

Innodb_redo_log_enabled

重做日志是启用还是禁用。请参见 禁用重做日志。Whether redo logging is enabled or disabled. See Disabling Redo Logging.

Innodb_redo_log_capacity_resized

上一次完成的容量调整操作后，所有重做日志文件的总重做日志容量（以字节为单位）。该值包括普通和备用重做日志文件。The total redo log capacity for all redo log files, in bytes, after the last completed capacity resize operation. The value includes ordinary and spare redo log files.

如果没有待处理的缩小操作，Innodb_redo_log_capacity_resized 应该等于所使用的 innodb_redo_log_capacity 设置，或者如果使用了其他参数，则等于 ((innodb_log_files_in_group * innodb_log_file_size))。有关进一步说明，请参阅 innodb_redo_log_capacity 文档。扩展操作是即时完成的。If there is no pending resize down operation, Innodb_redo_log_capacity_resized should be equal to the innodb_redo_log_capacity setting if it's used, or it's ((innodb_log_files_in_group * innodb_log_file_size)) if those are used instead. See the innodb_redo_log_capacity documentation for further clarification. Resize up operations are instantaneous.

有关相关信息，请参阅 第 17.6.5 节，“重做日志”。For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_checkpoint_lsn

重做日志检查点 LSN。有关相关信息，请参见 第 17.6.5 节，“重做日志”。The redo log checkpoint LSN. For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_current_lsn

当前的 LSN 表示重做日志缓冲区中最后写入的位置。InnoDB 在 MySQL 进程内部将数据写入重做日志缓冲区，然后才请求操作系统将数据写入当前的重做日志文件。有关相关信息，请参见 第 17.6.5 节，“重做日志”。The current LSN represents the last written position in the redo log buffer. InnoDB writes data to the redo log buffer inside the MySQL process before requesting that the operating system write the data to the current redo log file. For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_flushed_to_disk_lsn

已刷新到磁盘的 LSN。InnoDB 首先将数据写入重做日志，然后请求操作系统将数据刷新到磁盘。已刷新到磁盘的 LSN 表示 InnoDB 知道已被刷新到磁盘的重做日志中的最后位置。有关相关信息，请参见 第 17.6.5 节，“重做日志”。The flushed-to-disk LSN. InnoDB first writes data to the redo log and then requests that the operating system flush the data to disk. The flushed-to-disk LSN represents the last position in the redo log that InnoDB knows has been flushed to disk. For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_logical_size

一个以字节为单位的数据大小值，表示包含正在使用的重做日志数据的 LSN 范围，从重做日志使用者所需的最旧块到最新写入的块。有关相关信息，请参见 第 17.6.5 节，“重做日志”。A data size value, in bytes, representing the LSN range containing in-use redo log data, spanning from the oldest block required by redo log consumers to the latest written block. For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_physical_size

当前所有磁盘上的重做日志文件占用的磁盘空间字节数，不包括备用重做日志文件。有关相关信息，请参见第 17.6.5 节，“重做日志”。The amount of disk space in bytes currently consumed by all redo log files on disk, excluding spare redo log files. For related information, see Section 17.6.5, “Redo Log”.

Innodb_redo_log_read_only

重做日志是否为只读。Whether the redo log is read-only.

Innodb_redo_log_resize_status

重做日志大小调整状态，指示重做日志容量调整机制的当前状态。可能的值包括：The redo log resize status indicating the current state of the redo log capacity resize mechanism. Possible values include:

放大操作是瞬时的，因此没有待处理状态。A resize up operation is instantaneous and therefore has no pending status.

Innodb_redo_log_uuid

重做日志 UUID。The redo log UUID.

Innodb_row_lock_current_waits

当前因对 InnoDB 表的操作而等待的 行锁 数量。The number of row locks currently waited for by operations on InnoDB tables.

Innodb_row_lock_time

获取 InnoDB 表的 行锁 所花费的总时间，以毫秒为单位。The total time spent in acquiring row locks for InnoDB tables, in milliseconds.

Innodb_row_lock_time_avg

获取 行锁 对于 InnoDB 表的平均时间，单位为毫秒。The average time to acquire a row lock for InnoDB tables, in milliseconds.

Innodb_row_lock_time_max

获取 行锁 对于 InnoDB 表的最长时间，单位为毫秒。The maximum time to acquire a row lock for InnoDB tables, in milliseconds.

Innodb_row_lock_waits Innodb_row_lock_waits

在 InnoDB 表上操作时需要等待 行锁 的次数。The number of times operations on InnoDB tables had to wait for a row lock.

Innodb_rows_deleted Innodb_rows_deleted

从 InnoDB 表中删除的行数。The number of rows deleted from InnoDB tables.

Innodb_rows_inserted Innodb_rows_inserted

插入到 InnoDB 表中的行数。The number of rows inserted into InnoDB tables.

Innodb_rows_read Innodb_rows_read

从 InnoDB 表中读取的行数。The number of rows read from InnoDB tables.

Innodb_rows_updated Innodb_rows_updated

估计在InnoDB表中更新的行数。The estimated number of rows updated in InnoDB tables.

Innodb_system_rows_deleted

从属于系统创建模式的InnoDB表中删除的行数。The number of rows deleted from InnoDB tables belonging to system-created schemas.

Innodb_system_rows_inserted

插入到属于系统创建模式的InnoDB表中的行数。The number of rows inserted into InnoDB tables belonging to system-created schemas.

Innodb_system_rows_updated

更新属于系统创建模式的InnoDB表中的行数。The number of rows updated in InnoDB tables belonging to system-created schemas.

Innodb_system_rows_read

从属于系统创建模式的InnoDB表中读取的行数。The number of rows read from InnoDB tables belonging to system-created schemas.

Innodb_truncated_status_writes

执行 SHOW ENGINE INNODB STATUS 语句时输出被截断的次数。The number of times output from the SHOW ENGINE INNODB STATUS statement has been truncated.

Innodb_undo_tablespaces_active

活动撤销表空间的数量。包括隐式（InnoDB 创建的）和显式（用户创建的）撤销表空间。有关撤销表空间的详细信息，请参见 第 17.6.3.4 节，“撤销表空间”。The number of active undo tablespaces. Includes both implicit (InnoDB-created) and explicit (user-created) undo tablespaces. For information about undo tablespaces, see Section 17.6.3.4, “Undo Tablespaces”.

Innodb_undo_tablespaces_explicit

用户创建的撤销表空间数量。有关撤销表空间的详细信息，请参见 第 17.6.3.4 节，“撤销表空间”。The number of user-created undo tablespaces. For information about undo tablespaces, see Section 17.6.3.4, “Undo Tablespaces”.

Innodb_undo_tablespaces_implicit

InnoDB 创建的撤销表空间数量。MySQL 实例初始化时，InnoDB 会创建两个默认的撤销表空间。有关撤销表空间的信息，请参见 第 17.6.3.4 节，“撤销表空间”。The number of undo tablespaces created by InnoDB. Two default undo tablespaces are created by InnoDB when the MySQL instance is initialized. For information about undo tablespaces, see Section 17.6.3.4, “Undo Tablespaces”.

Innodb_undo_tablespaces_total Innodb_undo_tablespaces_total

撤销表空间的总数，包括隐式（InnoDB 创建的）和显式（用户创建的）撤销表空间，包含活跃和非活跃的表空间。有关撤销表空间的信息，请参见 第 17.6.3.4 节，“撤销表空间”。The total number of undo tablespaces. Includes both implicit (InnoDB-created) and explicit (user-created) undo tablespaces, active and inactive. For information about undo tablespaces, see Section 17.6.3.4, “Undo Tablespaces”.

Key_blocks_not_flushed Key_blocks_not_flushed

MyISAM 键缓存中已更改但尚未刷新到磁盘的键块数。The number of key blocks in the MyISAM key cache that have changed but have not yet been flushed to disk.

Key_blocks_unused Key_blocks_unused

MyISAM 键缓存中未使用的块数。您可以使用此值来确定键缓存的使用量；请参阅 key_buffer_size 在 第 7.1.8 节，“服务器系统变量” 的讨论。The number of unused blocks in the MyISAM key cache. You can use this value to determine how much of the key cache is in use; see the discussion of key_buffer_size in Section 7.1.8, “Server System Variables”.

Key_blocks_used Key_blocks_used

MyISAM 键缓存中已使用的块数。此值是一个高水位标记，表示曾经同时使用的最大块数。The number of used blocks in the MyISAM key cache. This value is a high-water mark that indicates the maximum number of blocks that have ever been in use at one time.

Key_read_requests Key_read_requests

从 MyISAM 键缓存中读取键块的请求次数。The number of requests to read a key block from the MyISAM key cache.

Key_reads Key_reads

从磁盘将关键块物理读取到MyISAM关键缓存中的次数。如果Key_reads数值很大，那么你的key_buffer_size值可能太小。缓存未命中率可以计算为Key_reads/Key_read_requests。The number of physical reads of a key block from disk into the MyISAM key cache. If Key_reads is large, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.

Key_write_requests Key_write_requests

请求将关键块写入MyISAM关键缓存的次数。The number of requests to write a key block to the MyISAM key cache.

Key_writes Key_writes

从 MyISAM 键缓存写入磁盘的键块物理写入次数。The number of physical writes of a key block from the MyISAM key cache to disk.

Last_query_cost Last_query_cost

查询优化器计算的最后一个已编译查询的总成本。这对于比较同一查询的不同查询计划的成本非常有用。默认值 0 表示尚未编译任何查询。默认值为 0。Last_query_cost 的作用范围是会话级别。The total cost of the last compiled query as computed by the query optimizer. This is useful for comparing the cost of different query plans for the same query. The default value of 0 means that no query has been compiled yet. The default value is 0. Last_query_cost has session scope.

此变量显示具有多个查询块的查询的成本，将每个查询块的成本估算相加，估算不可缓存子查询的执行次数，并将这些查询块的成本乘以子查询的执行次数。This variable shows the cost of queries that have multiple query blocks, summing the cost estimates of each query block, estimating how many times non-cacheable subqueries are executed, and multiplying the cost of those query blocks by the number of subquery executions.

Last_query_partial_plans Last_query_partial_plans

查询优化器在为上一个查询构建执行计划时所进行的迭代次数。The number of iterations the query optimizer made in execution plan construction for the previous query.

Last_query_partial_plans 具有会话范围。Last_query_partial_plans has session scope.

Locked_connects Locked_connects

第 8.2.20 节，“帐户锁定”已弃用的同义词.The number of attempts to connect to locked user accounts. For information about account locking and unlocking, see Section 8.2.20, “Account Locking”.

Max_execution_time_exceeded Max_execution_time_exceeded

执行超时被超过的 SELECT 语句的数量。The number of SELECT statements for which the execution timeout was exceeded.

Max_execution_time_set Max_execution_time_set

设置了非零执行超时的 SELECT 语句的数量。这包括包含非零 MAX_EXECUTION_TIME 优化器提示的语句，以及未包含此类提示但在 max_execution_time 系统变量指示的超时为非零的情况下执行的语句。The number of SELECT statements for which a nonzero execution timeout was set. This includes statements that include a nonzero MAX_EXECUTION_TIME optimizer hint, and statements that include no such hint but execute while the timeout indicated by the max_execution_time system variable is nonzero.

Max_execution_time_set_failed Max_execution_time_set_failed

尝试设置执行超时失败的 SELECT 语句的数量。The number of SELECT statements for which the attempt to set an execution timeout failed.

Max_used_connections Max_used_connections

自服务器启动以来同时使用的最大连接数。The maximum number of connections that have been in use simultaneously since the server started.

Max_used_connections_time Max_used_connections_time

Max_used_connections 达到其当前值的时间。The time at which Max_used_connections reached its current value.

Not_flushed_delayed_rows Not_flushed_delayed_rows

此状态变量已被弃用（因为不支持 DELAYED 插入）；预计将在未来版本中移除。This status variable is deprecated (because DELAYED inserts are not supported); expect it to be removed in a future release.

mecab_charset mecab_charset

MeCab 全文解析器插件当前使用的字符集。有关相关信息，请参阅第 14.9.9 节，“MeCab 全文解析器插件”。The character set currently used by the MeCab full-text parser plugin. For related information, see Section 14.9.9, “MeCab Full-Text Parser Plugin”.

Ongoing_anonymous_transaction_count Ongoing_anonymous_transaction_count

显示已标记为匿名的正在进行的事务数量。这可用于确保没有其他事务正在等待处理。Shows the number of ongoing transactions which have been marked as anonymous. This can be used to ensure that no further transactions are waiting to be processed.

Ongoing_anonymous_gtid_violating_transaction_count Ongoing_anonymous_gtid_violating_transaction_count

该状态变量仅在调试版本中可用。显示使用 gtid_next=ANONYMOUS 且违反 GTID 一致性的正在进行的事务数量。This status variable is only available in debug builds. Shows the number of ongoing transactions which use gtid_next=ANONYMOUS and that violate GTID consistency.

Ongoing_automatic_gtid_violating_transaction_count Ongoing_automatic_gtid_violating_transaction_count

此状态变量仅在调试版本中可用。显示使用 gtid_next=AUTOMATIC 并且违反 GTID 一致性的正在进行的事务数量。This status variable is only available in debug builds. Shows the number of ongoing transactions which use gtid_next=AUTOMATIC and that violate GTID consistency.

Open_files Open_files

打开的文件数量。此计数包括服务器打开的常规文件。不包括其他类型的文件，例如套接字或管道。此外，该计数不包括存储引擎使用其自身内部函数而不是通过服务器级别打开的文件。The number of files that are open. This count includes regular files opened by the server. It does not include other types of files such as sockets or pipes. Also, the count does not include files that storage engines open using their own internal functions rather than asking the server level to do so.

Open_streams Open_streams

正在打开的流的数量（主要用于日志记录）。The number of streams that are open (used mainly for logging).

Open_table_definitions Open_table_definitions

缓存表定义的数量。The number of cached table definitions.

Open_tables Open_tables

开放的桌子数量。The number of tables that are open.

Opened_files Opened_files

使用 my_open()（一个 mysys 库函数）打开的文件数量。服务器中那些在不使用此函数的情况下打开文件的部分不会增加计数。The number of files that have been opened with my_open() (a mysys library function). Parts of the server that open files without using this function do not increment the count.

Opened_table_definitions Opened_table_definitions

已缓存的表定义数量。The number of table definitions that have been cached.

Opened_tables Opened_tables

已打开的表的数量。如果 Opened_tables 很大，那么你的 table_open_cache 值可能太小。The number of tables that have been opened. If Opened_tables is big, your table_open_cache value is probably too small.

Performance_schema_xxxPerformance_schema_xxx

性能模式状态变量列在 第 29.16 节，“性能模式状态变量” 中。这些变量提供有关由于内存限制而无法加载或创建的仪器的信息。Performance Schema status variables are listed in Section 29.16, “Performance Schema Status Variables”. These variables provide information about instrumentation that could not be loaded or created due to memory constraints.

Prepared_stmt_count Prepared_stmt_count

当前准备好的语句数量。（语句的最大数量由 max_prepared_stmt_count 系统变量给出。）The current number of prepared statements. (The maximum number of statements is given by the max_prepared_stmt_count system variable.)

Queries Queries

服务器执行的语句数量。该变量包括在存储程序中执行的语句，这与 Questions 变量不同。它不计算 COM_PING 或 COM_STATISTICS 命令。The number of statements executed by the server. This variable includes statements executed within stored programs, unlike the Questions variable. It does not count COM_PING or COM_STATISTICS commands.

本节开头的讨论说明了如何将这个语句计数状态变量与其他此类变量关联起来。The discussion at the beginning of this section indicates how to relate this statement-counting status variable to other such variables.

Questions Questions

服务器执行的语句数量。这只包括客户端发送到服务器的语句，而不包括存储程序内执行的语句，这与 Queries 变量不同。该变量不计算 COM_PING、COM_STATISTICS、COM_STMT_PREPARE、COM_STMT_CLOSE 或 COM_STMT_RESET 命令。The number of statements executed by the server. This includes only statements sent to the server by clients and not statements executed within stored programs, unlike the Queries variable. This variable does not count COM_PING, COM_STATISTICS, COM_STMT_PREPARE, COM_STMT_CLOSE, or COM_STMT_RESET commands.

本节开头的讨论说明了如何将这个语句计数状态变量与其他此类变量关联起来。The discussion at the beginning of this section indicates how to relate this statement-counting status variable to other such variables.

Replica_open_temp_tables Replica_open_temp_tables

Replica_open_temp_tables 显示复制 SQL 线程当前打开的临时表的数量。如果该值大于零，则关闭副本是不安全的；请参见 第 19.5.1.31 节，“复制和临时表”。此变量报告 所有 复制通道打开的临时表总数。Replica_open_temp_tables shows the number of temporary tables that the replication SQL thread currently has open. If the value is greater than zero, it is not safe to shut down the replica; see Section 19.5.1.31, “Replication and Temporary Tables”. This variable reports the total count of open temporary tables for all replication channels.

Resource_group_supported Resource_group_supported

指示是否支持资源组功能。Indicates whether the resource group feature is supported.

在某些平台或 MySQL 服务器配置中，资源组不可用或存在限制。特别是，对于某些安装方法，Linux 系统可能需要手动操作。详情请参阅 资源组限制。On some platforms or MySQL server configurations, resource groups are unavailable or have limitations. In particular, Linux systems might require a manual step for some installation methods. For details, see Resource Group Restrictions.

Rpl_semi_sync_master_clients Rpl_semi_sync_master_clients

半同步副本的数量。The number of semisynchronous replicas.

已弃用的 Rpl_semi_sync_source_clients 同义词。Deprecated synonym for Rpl_semi_sync_source_clients.

Rpl_semi_sync_master_net_avg_wait_time Rpl_semi_sync_master_net_avg_wait_time

已弃用的 Rpl_semi_sync_source_net_avg_wait_time 同义词。Deprecated synonym for Rpl_semi_sync_source_net_avg_wait_time.

Rpl_semi_sync_master_net_wait_time Rpl_semi_sync_master_net_wait_time

已弃用的 Rpl_semi_sync_source_net_wait_time 同义词。Deprecated synonym for Rpl_semi_sync_source_net_wait_time.

Rpl_semi_sync_master_net_waits

源等待副本回复的总次数。The total number of times the source waited for replica replies.

拒绝查询，其选择列表、Rpl_semi_sync_source_net_waits.Deprecated synonym for Rpl_semi_sync_source_net_waits.

Rpl_semi_sync_master_no_times

拒绝查询，其选择列表、Rpl_semi_sync_source_no_times.Deprecated synonym for Rpl_semi_sync_source_no_times.

Rpl_semi_sync_master_no_tx

拒绝查询，其选择列表、Rpl_semi_sync_source_no_tx.Deprecated synonym for Rpl_semi_sync_source_no_tx.

Rpl_semi_sync_master_status

已弃用的 Rpl_semi_sync_source_status 的同义词。Deprecated synonym for Rpl_semi_sync_source_status.

Rpl_semi_sync_master_timefunc_failures

已弃用的 Rpl_semi_sync_source_timefunc_failures 的同义词。Deprecated synonym for Rpl_semi_sync_source_timefunc_failures.

Rpl_semi_sync_master_tx_avg_wait_time

已弃用的同义词，指向 Rpl_semi_sync_source_tx_avg_wait_time。Deprecated synonym for Rpl_semi_sync_source_tx_avg_wait_time.

Rpl_semi_sync_master_tx_wait_time

已弃用的同义词，指向 Rpl_semi_sync_source_tx_wait_time。Deprecated synonym for Rpl_semi_sync_source_tx_wait_time.

Rpl_semi_sync_master_tx_waits

已弃用的同义词，指 Rpl_semi_sync_source_tx_waits。Deprecated synonym for Rpl_semi_sync_source_tx_waits.

Rpl_semi_sync_master_wait_pos_backtraverse

已弃用的同义词，指 Rpl_semi_sync_source_wait_pos_backtraverse。Deprecated synonym for Rpl_semi_sync_source_wait_pos_backtraverse.

Rpl_semi_sync_master_wait_sessions

已弃用的 Rpl_semi_sync_source_wait_sessions 的同义词。Deprecated synonym for Rpl_semi_sync_source_wait_sessions.

Rpl_semi_sync_master_yes_tx

已弃用的 Rpl_semi_sync_source_yes_tx 的同义词。Deprecated synonym for Rpl_semi_sync_source_yes_tx.

Rpl_semi_sync_source_clients

半同步副本的数量。The number of semisynchronous replicas.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_net_avg_wait_time

源等待副本回复的平均时间，单位为微秒。此变量始终为 0，并且已弃用；预计将在将来的版本中移除。The average time in microseconds the source waited for a replica reply. This variable is always 0, and is deprecated; expect it to be removed in a future version.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_net_wait_time

源等待副本回复的总时间（微秒）。该变量始终为0，已弃用；预计将在未来版本中删除。The total time in microseconds the source waited for replica replies. This variable is always 0, and is deprecated; expect it to be removed in a future version.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_net_waits

源等待副本回复的总次数。The total number of times the source waited for replica replies.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_no_times

源关闭半同步复制的次数。The number of times the source turned off semisynchronous replication.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_no_tx

未被副本成功确认的提交次数。The number of commits that were not acknowledged successfully by a replica.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_status

源上半同步复制当前是否正在运行。如果插件已启用且已发生提交确认，则值为ON。如果插件未启用或由于提交确认超时而源回退到异步复制，则值为OFF。Whether semisynchronous replication currently is operational on the source. The value is ON if the plugin has been enabled and a commit acknowledgment has occurred. It is OFF if the plugin is not enabled or the source has fallen back to asynchronous replication due to commit acknowledgment timeout.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_timefunc_failures

源在调用诸如gettimeofday()等时间函数失败的次数。The number of times the source failed when calling time functions such as gettimeofday().

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_tx_avg_wait_time

源等待每笔事务的平均时间（微秒）。The average time in microseconds the source waited for each transaction.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_tx_wait_time Rpl_semi_sync_source_tx_wait_time

源等待事务的总时间（微秒）。The total time in microseconds the source waited for transactions.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_tx_waits Rpl_semi_sync_source_tx_waits

源等待事务的总次数。The total number of times the source waited for transactions.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_wait_pos_backtraverse Rpl_semi_sync_source_wait_pos_backtraverse

源等待具有比之前等待的事件更低二进制坐标的事件的总次数。当事务开始等待回复的顺序与它们的二进制日志事件被写入的顺序不同时，可能会发生这种情况。The total number of times the source waited for an event with binary coordinates lower than events waited for previously. This can occur when the order in which transactions start waiting for a reply is different from the order in which their binary log events are written.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_wait_sessions Rpl_semi_sync_source_wait_sessions

当前正在等待副本回复的会话数。The number of sessions currently waiting for replica replies.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_source_yes_tx

被副本成功确认的提交次数。The number of commits that were acknowledged successfully by a replica.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_replica_status

显示半同步复制在副本上当前是否正在运行。如果插件已启用且复制 I/O（接收器）线程正在运行，则为 ON，否则为 OFF。Shows whether semisynchronous replication is currently operational on the replica. This is ON if the plugin has been enabled and the replication I/O (receiver) thread is running, OFF otherwise.

当源上安装了 rpl_semi_sync_source 插件（semisync_source.so 库）时可用。Available when the rpl_semi_sync_source plugin (semisync_source.so library) is installed on the source.

Rpl_semi_sync_slave_status

已弃用的 Rpl_semi_sync_replica_status 同义词。Deprecated synonym for Rpl_semi_sync_replica_status.

Rsa_public_key

该变量的值是由sha256_password（已弃用）身份验证插件用于基于 RSA 密钥对的密码交换的公钥。仅当服务器成功初始化由系统变量sha256_password_private_key_path和sha256_password_public_key_path指定的文件中的私钥和公钥时，该值才非空。Rsa_public_key的值来自后者文件。The value of this variable is the public key used by the sha256_password (deprecated) authentication plugin for RSA key pair-based password exchange. The value is nonempty only if the server successfully initializes the private and public keys in the files named by the sha256_password_private_key_path and sha256_password_public_key_path system variables. The value of Rsa_public_key comes from the latter file.

有关 sha256_password 的信息，请参见 第 8.4.1.3 节，“SHA-256 可插拔身份验证”。For information about sha256_password, see Section 8.4.1.3, “SHA-256 Pluggable Authentication”.

Secondary_engine_execution_count

仅适用于 MySQL HeatWave。更多信息请参见 状态变量。For use with MySQL HeatWave only. See Status Variables, for more information.

Select_full_join

由于未使用索引而执行表扫描的连接数量。如果此值不为 0，您应仔细检查表的索引。The number of joins that perform table scans because they do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.

Select_full_range_join

在引用表上使用范围搜索的连接次数。The number of joins that used a range search on a reference table.

Select_range Select_range

在第一个表上使用范围的连接次数。即使该值相当大，这通常也不是一个关键问题。The number of joins that used ranges on the first table. This is normally not a critical issue even if the value is quite large.

Select_range_check

在每行之后检查键使用的无键连接数。如果此值不为 0，您应仔细检查表的索引。The number of joins without keys that check for key usage after each row. If this is not 0, you should carefully check the indexes of your tables.

Select_scan

对第一个表执行全表扫描的连接数。The number of joins that did a full scan of the first table.

Slave_open_temp_tables Slave_open_temp_tables

已弃用的别名，指代 Replica_open_temp_tables。Deprecated alias for Replica_open_temp_tables.

Slave_rows_last_search_algorithm_used Slave_rows_last_search_algorithm_used

已弃用的别名，指代 Replica_rows_last_search_algorithm_used。Deprecated alias for Replica_rows_last_search_algorithm_used.

Slow_launch_threads Slow_launch_threads

创建时间超过 slow_launch_time 秒的线程数量。The number of threads that have taken more than slow_launch_time seconds to create.

Slow_queries Slow_queries

执行时间超过 long_query_time 秒的查询数量。无论是否启用慢查询日志，该计数器都会增加。有关该日志的信息，请参见 第 7.4.5 节，“慢查询日志”。The number of queries that have taken more than long_query_time seconds. This counter increments regardless of whether the slow query log is enabled. For information about that log, see Section 7.4.5, “The Slow Query Log”.

Sort_merge_passes Sort_merge_passes

排序算法必须进行的合并次数。如果这个值很大，你应该考虑增加系统变量 sort_buffer_size 的值。The number of merge passes that the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.

Sort_range Sort_range

使用范围完成的排序数量。The number of sorts that were done using ranges.

Sort_rows Sort_rows

已排序行的数量。The number of sorted rows.

Sort_scan Sort_scan

通过扫描表格完成的排序次数。The number of sorts that were done by scanning the table.

Ssl_accept_renegotiates Ssl_accept_renegotiates

建立连接所需的协商次数。The number of negotiates needed to establish the connection.

Ssl_accepts Ssl_accepts

接受的 SSL 连接数。The number of accepted SSL connections.

Ssl_callback_cache_hits Ssl_callback_cache_hits

回调缓存命中的次数。The number of callback cache hits.

Ssl_cipher Ssl_cipher

当前的加密密码（未加密连接时为空）。The current encryption cipher (empty for unencrypted connections).

Ssl_cipher_list

可能的 SSL 密码列表（非 SSL 连接为空）。如果 MySQL 支持 TLSv1.3，则该值包括可能的 TLSv1.3 密码套件。请参见 第 8.3.2 节，“加密连接 TLS 协议和密码”。The list of possible SSL ciphers (empty for non-SSL connections). If MySQL supports TLSv1.3, the value includes the possible TLSv1.3 ciphersuites. See Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”.

Ssl_client_connects

尝试与启用 SSL 的复制源服务器建立 SSL 连接的次数。The number of SSL connection attempts to an SSL-enabled replication source server.

Ssl_connect_renegotiates

建立与启用 SSL 的复制源服务器连接所需的协商次数。The number of negotiates needed to establish the connection to an SSL-enabled replication source server.

Ssl_ctx_verify_depth

SSL 上下文验证深度（链中有多少证书会被测试）。The SSL context verification depth (how many certificates in the chain are tested).

Ssl_ctx_verify_mode

SSL 上下文验证模式。The SSL context verification mode.

Ssl_default_timeout

默认的 SSL 超时。The default SSL timeout.

Ssl_finished_accepts

与服务器成功的 SSL 连接数。The number of successful SSL connections to the server.

Ssl_finished_connects

成功连接到启用 SSL 的复制源服务器的副本连接数。The number of successful replica connections to an SSL-enabled replication source server.

Ssl_server_not_after

SSL 证书有效的最后日期。要检查 SSL 证书的到期信息，请使用以下语句：The last date for which the SSL certificate is valid. To check SSL certificate expiration information, use this statement:

mysql> SHOW STATUS LIKE 'Ssl_server_not%';
+-----------------------+--------------------------+
| Variable_name         | Value                    |
+-----------------------+--------------------------+
| Ssl_server_not_after  | Apr 28 14:16:39 2025 GMT |
| Ssl_server_not_before | May  1 14:16:39 2015 GMT |
+-----------------------+--------------------------+

Ssl_server_not_before

SSL 证书开始生效的日期。The first date for which the SSL certificate is valid.

Ssl_session_cache_hits

SSL 会话缓存命中的次数。The number of SSL session cache hits.

Ssl_session_cache_misses

SSL 会话缓存未命中的次数。The number of SSL session cache misses.

Ssl_session_cache_mode

SSL 会话缓存模式。当 ssl_session_cache_mode 服务器变量的值为 ON 时，Ssl_session_cache_mode 状态变量的值为 SERVER。The SSL session cache mode. When the value of the ssl_session_cache_mode server variable is ON, the value of the Ssl_session_cache_mode status variable is SERVER.

Ssl_session_cache_overflows

SSL 会话缓存溢出的次数。The number of SSL session cache overflows.

Ssl_session_cache_size

SSL 会话缓存大小。The SSL session cache size.

Ssl_session_cache_timeout

缓存中 SSL 会话的超时时间（秒）。The timeout value in seconds of SSL sessions in the cache.

Ssl_session_cache_timeouts

SSL 会话缓存超时的次数。The number of SSL session cache timeouts.

Ssl_sessions_reused

如果当前 MySQL 会话未使用 TLS，或 TLS 会话未被重用，则此值等于 0；否则等于 1。This is equal to 0 if TLS was not used in the current MySQL session, or if a TLS session has not been reused; otherwise it is equal to 1.

Ssl_sessions_reused 具有会话范围。Ssl_sessions_reused has session scope.

Ssl_used_session_cache_entries

使用了多少 SSL 会话缓存条目。How many SSL session cache entries were used.

Ssl_verify_depth

用于复制 SSL 连接的验证深度。The verification depth for replication SSL connections.

Ssl_verify_mode

服务器在使用 SSL 的连接中使用的验证模式。该值是一个位掩码；位在 openssl/ssl.h 头文件中定义：The verification mode used by the server for a connection that uses SSL. The value is a bitmask; bits are defined in the openssl/ssl.h header file:

# define SSL_VERIFY_NONE                 0x00
# define SSL_VERIFY_PEER                 0x01
# define SSL_VERIFY_FAIL_IF_NO_PEER_CERT 0x02
# define SSL_VERIFY_CLIENT_ONCE          0x04

SSL_VERIFY_PEER 表示服务器请求客户端证书。如果客户端提供证书，服务器将执行验证，并且仅在验证成功时继续。SSL_VERIFY_CLIENT_ONCE 表示客户端证书请求仅在初始握手中执行一次。SSL_VERIFY_PEER indicates that the server asks for a client certificate. If the client supplies one, the server performs verification and proceeds only if verification is successful. SSL_VERIFY_CLIENT_ONCE indicates that a request for the client certificate is performed only in the initial handshake.

Ssl_version

连接的 SSL 协议版本（例如，TLSv1.2）。如果连接未加密，则该值为空。The SSL protocol version of the connection (for example, TLSv1.2). If the connection is not encrypted, the value is empty.

Table_locks_immediate Table_locks_immediate

请求表锁能立即被授予的次数。The number of times that a request for a table lock could be granted immediately.

Table_locks_waited Table_locks_waited

请求表锁时无法立即授予并需要等待的次数。如果这个次数很高并且您遇到性能问题，您应首先优化查询，然后要么拆分您的表或表群，要么使用复制。The number of times that a request for a table lock could not be granted immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.

Table_open_cache_hits Table_open_cache_hits

打开表缓存查找的命中次数。The number of hits for open tables cache lookups.

Table_open_cache_misses Table_open_cache_misses

打开表缓存查找未命中的次数。The number of misses for open tables cache lookups.

Table_open_cache_overflows

打开表缓存的溢出次数。这是在表被打开或关闭之后，缓存实例有未使用的条目且实例的大小大于 table_open_cache / table_open_cache_instances 的次数。The number of overflows for the open tables cache. This is the number of times, after a table is opened or closed, a cache instance has an unused entry and the size of the instance is larger than table_open_cache / table_open_cache_instances.

Tc_log_max_pages_used

对于由 mysqld 用作内部 XA 事务恢复的事务协调器时使用的基于内存映射的日志实现，该变量指示自服务器启动以来日志使用的最大页数。如果 Tc_log_max_pages_used 与 Tc_log_page_size 的乘积总是明显小于日志大小，则日志大小大于必要值，可以减小。(该大小由 --log-tc-size 选项设置。该变量未使用：二进制日志恢复不需要它，并且除非支持两阶段提交且支持 XA 事务的存储引擎数量大于 1，否则不会使用基于内存映射的恢复日志方法。(InnoDB 是唯一适用的引擎。)For the memory-mapped implementation of the log that is used by mysqld when it acts as the transaction coordinator for recovery of internal XA transactions, this variable indicates the largest number of pages used for the log since the server started. If the product of Tc_log_max_pages_used and Tc_log_page_size is always significantly less than the log size, the size is larger than necessary and can be reduced. (The size is set by the --log-tc-size option. This variable is unused: It is unneeded for binary log-based recovery, and the memory-mapped recovery log method is not used unless the number of storage engines that are capable of two-phase commit and that support XA transactions is greater than one. (InnoDB is the only applicable engine.)

Tc_log_page_size

用于 XA 恢复日志内存映射实现的页面大小。默认值通过 getpagesize() 确定。由于与 Tc_log_max_pages_used 描述的原因相同，该变量未使用。The page size used for the memory-mapped implementation of the XA recovery log. The default value is determined using getpagesize(). This variable is unused for the same reasons as described for Tc_log_max_pages_used.

Tc_log_page_waits

对于恢复日志的内存映射实现，每当服务器无法提交事务并且必须等待日志中的空闲页面时，该变量会递增。如果此值很大，您可能需要增加日志大小（使用 --log-tc-size 选项）。对于基于二进制日志的恢复，每当二进制日志无法关闭，因为存在正在进行的两阶段提交时，该变量会递增。（关闭操作会等待所有此类事务完成。）For the memory-mapped implementation of the recovery log, this variable increments each time the server was not able to commit a transaction and had to wait for a free page in the log. If this value is large, you might want to increase the log size (with the --log-tc-size option). For binary log-based recovery, this variable increments each time the binary log cannot be closed because there are two-phase commits in progress. (The close operation waits until all such transactions are finished.)

Telemetry_metrics_supported

是否支持服务器遥测指标。Whether server telemetry metrics is supported.

欲了解更多信息，请参阅 MySQL 源代码文档中的 服务器遥测指标服务 部分。For more information, see the Server telemetry metrics service section in the MySQL Source Code documentation.

telemetry.live_sessions

显示当前使用遥测的会话数量。当卸载遥测组件时，这可能很有用，以监控有多少会话阻止卸载操作。Displays the current number of sessions instrumented with telemetry. This can be useful when unloading the Telemetry component, to monitor how many sessions are blocking the unload operation.

有关更多信息，请参阅 MySQL 源代码文档中的 服务器遥测跟踪服务 部分以及 第 35 章，遥测。For more information, see the Server telemetry traces service section in the MySQL Source Code documentation and Chapter 35, Telemetry.

Telemetry_traces_supported

是否支持服务器遥测跟踪。Whether server telemetry traces is supported.

欲了解更多信息，请参阅 MySQL 源代码文档中的 服务器遥测跟踪服务 部分。For more information, see the Server telemetry traces service section in the MySQL Source Code documentation.

Threads_cached Threads_cached

线程缓存中的线程数量。The number of threads in the thread cache.

Threads_connected Threads_connected

当前打开的连接数。The number of currently open connections.

Threads_created Threads_created

用于处理连接而创建的线程数。如果 Threads_created 很大，你可能需要增加 thread_cache_size 的值。缓存未命中率可以计算为 Threads_created/Connections。The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. The cache miss rate can be calculated as Threads_created/Connections.

Threads_running Threads_running

未处于睡眠状态的线程数。The number of threads that are not sleeping.

Tls_library_version Tls_library_version

用于此 MySQL 实例的 OpenSSL 库的运行时版本。The runtime version of the OpenSSL library that is in use for this MySQL instance.

Tls_sni_server_name Tls_sni_server_name

用于此会话的服务器名称指示（SNI），如果由客户端指定；否则为空。SNI 是 TLS 协议的一个扩展（OpenSSL 必须使用 TLS 扩展进行编译，该状态变量才会起作用）。MySQL 对 SNI 的实现仅代表客户端。The Server Name Indication (SNI) that is in use for this session, if specified by the client; otherwise, empty. SNI is an extension to the TLS protocol (OpenSSL must be compiled using TLS extensions for this status variable to function). The MySQL implementation of SNI represents the client-side only.

Uptime Uptime

服务器已运行的秒数。The number of seconds that the server has been up.

Uptime_since_flush_status Uptime_since_flush_status

自最近一次 FLUSH STATUS 语句以来的秒数。The number of seconds since the most recent FLUSH STATUS statement.