Spec-Zone .ru
спецификации, руководства, описания, API
|
The following table provides a list of the command-line options, server and status variables applicable within
mysqld
when it is running as an SQL node in a MySQL Cluster. For a table showing
all command-line options, server and status variables available for use
with mysqld,
see Section 5.1.1, "Server Option and Variable
Reference".
Table 17.9. MySQL Cluster mysqld Options and Variables: MySQLCluster NDB 7.3
Option or Variable Name | Command Line | System Variable | Scope |
---|---|---|---|
Option File | Status Variable | Dynamic | |
Notes | |||
N | N | Both | |
N | Y | N | |
The number of times that tables have been discovered |
|||
N | N | Session | |
N | Y | N | |
Number of times thread has been blocked while waiting for execution of an operation to complete in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked while waiting for execution of an operation to complete by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked while waiting for execution of an operation to complete by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of times thread has been blocked while waiting for a scan-based signal in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked while waiting for a scan-based signal by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked while waiting for a scan-based signal by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of times thread has been blocked waiting for a metadata-based signal in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked waiting for a metadata-based signal by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of times thread has been blocked waiting for a metadata-based signal by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Total time (in nanoseconds) spent waiting for some type of signal from the data nodes in this client session. |
|||
N | N | Global | |
N | Y | N | |
Total time (in nanoseconds) spent waiting for some type of signal from the data nodes by this slave. |
|||
N | N | Global | |
N | Y | N | |
Total time (in nanoseconds) spent waiting for some type of signal from the data nodes by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Amount of data (in bytes) sent to the data nodes in this client session. |
|||
N | N | Global | |
N | Y | N | |
Amount of data (in bytes) sent to the data nodes by this slave. |
|||
N | N | Global | |
N | Y | N | |
Amount of data (in bytes) sent to the data nodes by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Amount of data (in bytes) received from the data nodes in this client session. |
|||
N | N | Global | |
N | Y | N | |
Amount of data (in bytes) received from the data nodes by this slave. |
|||
N | N | Global | |
N | Y | N | |
Amount of data (in bytes) received from the data nodes by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of transactions started in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions started by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions started by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of transactions committed in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions committed by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions committed by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of transactions aborted in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions aborted by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions aborted by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of transactions aborted (may be greater than the sum of TransCommitCount and TransAbortCount) in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions aborted (may be greater than the sum of TransCommitCount and TransAbortCount) by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions aborted (may be greater than the sum of TransCommitCount and TransAbortCount) by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of operations based on or using primary keys in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of operations based on or using primary keys by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of operations based on or using primary keys by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of operations based on or using unique keys in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of operations based on or using unique keys by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of operations based on or using unique keys by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of table scans that have been started, including scans of internal tables, in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of table scans that have been started, including scans of internal tables, by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of table scans that have been started, including scans of internal tables, by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of range scans that have been started in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of range scans that have been started by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of range scans that have been started by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of scans that have been pruned to a single partition in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of scans that have been pruned to a single partition by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of scans that have been pruned to a single partition by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Number of batches of rows received in this client session. |
|||
N | N | Global | |
N | Y | N | |
Number of batches of rows received by this slave. |
|||
N | N | Global | |
N | Y | N | |
Number of batches of rows received by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Total number of rows that have been read in this client session. |
|||
N | N | Global | |
N | Y | N | |
Total number of rows that have been read by this slave. |
|||
N | N | Global | |
N | Y | N | |
Total number of rows that have been read by this MySQL Server (SQL node). |
|||
N | N | Session | |
N | Y | N | |
Total number of rows that have been read in this client session. |
|||
N | N | Global | |
N | Y | N | |
Total number of rows that have been read by this slave. |
|||
N | N | Global | |
N | Y | N | |
Total number of rows that have been read by this MySQL Server (SQL node). |
|||
N | N | Global | |
N | Y | N | |
Number of row change events received by the NDB binlog injector thread. |
|||
N | N | Global | |
N | Y | N | |
Number of row change events received by this MySQL Server (SQL node). |
|||
N | N | Global | |
N | Y | N | |
Number of events received, other than row change events, by the NDB binlog injector thread. |
|||
N | N | Global | |
N | Y | N | |
Number of events received, other than row change events, by this MySQL Server (SQL node). |
|||
N | N | Global | |
N | Y | N | |
Number of bytes of events received by the NDB binlog injector thread. |
|||
N | N | Global | |
N | Y | N | |
Number of bytes of events received by this MySQL Server (SQL node). |
|||
N | N | Global | |
N | Y | N | |
If the server is part of a MySQL Cluster, the value of this variable is the number of data nodes in the cluster |
|||
N | N | Global | |
N | Y | N | |
If the server is part of a MySQL Cluster involved in cluster replication, the value of this variable indicates the number of times that conflict resolution based on "greater timestamp wins" has been applied |
|||
N | N | Global | |
N | Y | N | |
If the server is part of a MySQL Cluster involved in cluster replication, the value of this variable indicates the number of times that "same timestamp wins" conflict resolution has been applied |
|||
N | N | Global | |
N | Y | N | |
Number of rows that have been found in conflict by the NDB$EPOCH() conflict detection function |
|||
N | N | Global | |
N | Y | N | |
Number of rows that have been found in conflict by the NDB$EPOCH_TRANS() conflict detection function |
|||
N | N | Global | |
N | Y | N | |
Number of rows found to be in conflict by a transactional conflict function |
|||
N | N | Global | |
N | Y | N | |
Total number of rows realigned after being found in conflict by a transactional conflict function. Includes Ndb_conflict_trans_row_conflict_count and any rows included in or dependent on conflicting transactions. |
|||
N | N | Global | |
N | Y | N | |
Number of transactions rejected after being found in conflict by a transactional conflict function. |
|||
N | N | Global | |
N | Y | N | |
The number of internal iterations required to commit an epoch transaction. Should be (slightly) greater than or equal to Ndb_conflict_trans_conflict_commit_count. |
|||
N | N | Global | |
N | Y | N | |
The number of epoch transactions committed after requiring transactional conflict handling. |
|||
N | Y | Global | |
N | N | Y | |
Sets the number of milliseconds to wait between processing sets of rows by OPTIMIZE TABLE on NDB tables. |
|||
N | Y | Session | |
N | N | Y | |
NDB tables are not persistent on disk: no schema files are created and the tables are not logged |
|||
N | Y | Session | |
N | N | Y | |
NDB tables created when this setting is enabled are not checkpointed to disk (although table schema files are created). The setting in effect when the table is created with or altered to use NDBCLUSTER persists for the lifetime of the table. |
|||
Y | Y | Both | |
Y | N | Y | |
NDB auto-increment prefetch size |
|||
Y | Y | Global | |
Y | N | N | |
The size (in bytes) to use for NDB transaction batches |
|||
Y | Y | Both | |
Y | N | Y | |
Specifies the size in bytes that large BLOB reads should be batched into. 0 = no limit. |
|||
Y | Y | Both | |
Y | N | Y | |
Specifies the size in bytes that large BLOB writes should be batched into. 0 = no limit. |
|||
Y | Y | Global | |
Y | N | Y | |
The number of milliseconds between checks of cluster SQL nodes made by the MySQL query cache |
|||
Y | Y | Global | |
Y | Y | N | |
The number of connections to the cluster used by MySQL |
|||
N | Y | Global | |
N | N | N | |
Enables pushing down of joins to data nodes |
|||
N | N | Global | |
N | Y | N | |
Provides the number of round trips to the NDB kernel made by operations |
|||
N | N | Global | |
N | Y | N | |
The total number of scans executed by NDB since the cluster was last started |
|||
N | N | Global | |
N | Y | N | |
The number of scans executed by NDB since the cluster was last started where partition pruning could be used |
|||
Y | N | ||
Y | N | N | |
The management server that distributes the cluster configuration |
|||
Y | Y | Global | |
Y | N | Y | |
Controls logging of MySQL Cluster schema, connection, and data distribution events in the MySQL error log |
|||
Y | Y | Both | |
Y | N | Y | |
Forces sending of buffers to NDB immediately, without waiting for other threads |
|||
N | Y | Both | |
N | N | Y | |
Use exact row count when planning queries |
|||
Y | Y | Global | |
Y | N | N | |
Cause a MySQL server acting as a slave to log mysql.ndb_apply_status updates received from its immediate master in its own binary log, using its own server ID. Effective only if the server is started with the --ndbcluster option. |
|||
Y | Y | Both | |
N | N | Y | |
Write updates to NDB tables in the binary log. Effective only if binary logging is enabled with --log-bin. |
|||
Y | Y | Global | |
N | N | Y | |
Insert mapping between epochs and binary log positions into the ndb_binlog_index table. Defaults to ON. Effective only if binary logging is enabled on the server. |
|||
Y | Y | Global | |
Y | N | N | |
Log originating server id and epoch in mysql.ndb_binlog_index table. |
|||
Y | Y | Global | |
Y | N | N | |
Write NDB transaction IDs in the binary log. Requires --log-bin-v1-events=OFF. |
|||
N | Y | Global | |
N | N | N | |
Whether NDB transaction IDs are written into the binary log. (Read-only.) |
|||
Y | Y | Global | |
Y | N | Y | |
Log complete rows (ON) or updates only (OFF) |
|||
Y | Y | Global | |
Y | N | Y | |
Toggles logging of updates on the master between updates (OFF) and writes (ON) |
|||
Y | Y | Global | |
Y | N | Y | |
When enabled, causes epochs in which there were no changes to be written to the ndb_apply_status and ndb_binlog_index tables, even when --log-slave-updates is enabled. |
|||
Y | Y | Global | |
Y | N | Y | |
When enabled, epochs in which there were no changes are written to the ndb_apply_status and ndb_binlog_index tables, even when log_slave_updates is enabled. |
|||
Y | N | ||
N | N | N | |
Enable or disable the ndb_transid_mysql_connection_map plugin; that is, enable or disable the INFORMATION_SCHEMA table having that name. |
|||
N | N | Global | |
N | Y | N | |
Number of reads executed on the data nodes by pushed-down joins |
|||
N | N | Global | |
N | Y | N | |
Number of joins that API nodes have attempted to push down to the data nodes |
|||
N | N | Global | |
N | Y | N | |
Number of joins that API nodes have tried to push down, but failed |
|||
N | N | Global | |
N | Y | N | |
Number of joins successfully pushed down and executed on the data nodes |
|||
Y | N | Global | |
Y | Y | N | |
MySQL Cluster node ID for this MySQL server |
|||
Y | N | ||
Y | N | N | |
Set the host (and port, if desired) for connecting to the management server |
|||
Y | Y | Global | |
Y | N | N | |
Time (in seconds) for the MySQL server to wait for connection to cluster management and data nodes before accepting MySQL client connections. |
|||
Y | Y | Global | |
Y | N | N | |
Time (in seconds) for the MySQL server to wait for NDB engine setup to complete. |
|||
Y | N | ||
Y | N | N | |
Enable NDB Cluster (if this version of MySQL supports it) |
|||
N | Y | Global | |
N | N | N | |
The name used for the NDB information database; read only. |
|||
Y | Y | Both | |
N | N | Y | |
Used for debugging only. |
|||
Y | Y | Both | |
N | N | Y | |
Used for debugging only. |
|||
Y | Y | Both | |
N | N | Y | |
Whether to show ndbinfo internal base tables in the mysql client. The default is OFF. |
|||
Y | Y | Both | |
N | N | Y | |
The prefix to use for naming ndbinfo internal base tables. Defaults to 'ndb$'. |
|||
N | Y | Global | |
N | N | N | |
The version of the ndbinfo engine; read only. |
|||
Y | Y | Global | |
Y | N | N | |
Sets the number of least significant bits in the server_id actually used for identifying the server, permitting NDB API applications to store application data in the most significant bits. server_id must be less than 2 to the power of this value. |
|||
N | Y | Session | |
N | N | Y | |
Allows batching of statements within a transaction. Disable AUTOCOMMIT to use. |
|||
N | Y | Global | |
N | N | N | |
Whether mysqld supports NDB Cluster tables (set by --ndbcluster option) |
|||
Y | Y | Both | |
Y | N | Y | |
Specifies that constraint checks on unique indexes (where these are supported) should be deferred until commit time. Not normally needed or used; for testing purposes only. |
|||
Y | Y | Both | |
Y | N | Y | |
Specifies that constraint checks should be deferred (where these are supported). Not normally needed or used; for testing purposes only. |
|||
Y | Y | Both | |
Y | N | Y | |
Default distribution for new tables in NDBCLUSTER (KEYHASH or LINHASH, default is KEYHASH) |
|||
Y | Y | Both | |
Y | N | Y | |
Default distribution for new tables in NDBCLUSTER (KEYHASH or LINHASH, default is KEYHASH) |
|||
Y | N | ||
Y | N | N | |
Determines how an SQL node chooses a cluster data node to use as transaction coordinator |
|||
Y | N | ||
Y | N | N | |
This is a threshold on the number of epochs to be behind before reporting binlog status |
|||
Y | N | ||
Y | N | N | |
This is a threshold on the percentage of free memory remaining before reporting binlog status |
|||
Y | Y | Both | |
Y | N | Y | |
Forces NDB to use a count of records during SELECT COUNT(*) query planning to speed up this type of query |
|||
N | N | Both | |
N | Y | N | |
If the server is acting as a MySQL Cluster node, then the value of this variable its node ID in the cluster |
|||
N | N | Both | |
N | Y | N | |
The host name or IP address of the Cluster management server. Formerly Ndb_connected_host |
|||
N | N | Both | |
N | Y | N | |
The port for connecting to the Cluster management server. Formerly Ndb_connected_port |
|||
N | N | Both | |
N | Y | N | |
Count of SHOW NDB STATUS statements |