PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-resolved.html
A number of limitations and related issues that existed in earlier versions of NDB Cluster have been resolved in NDB 8.0. These are described briefly in the following list: Database and table names. In NDB 7.6 and earlier, when using the NDB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-unsupported.html
A number of features supported by other storage engines are not supported for NDB tables. Trying to use any of these features in NDB Cluster does not cause errors in or of itself; however, errors may occur in applications that expects the features ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations.html
See Section 25.2.7.11, “Previous NDB Cluster Issues Resolved in NDB Cluster 8.0” for a list of issues in earlier releases that have been resolved in NDB Cluster 8.0. In the sections that follow, we discuss known limitations in current releases ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-innodb-usage.html
When comparing application feature requirements to the capabilities of InnoDB with NDB, some are clearly more compatible with one storage engine than the other. The following table lists supported application features according to the storage ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-arbitrator-validity-summary.html
The arbitrator_validity_summary table provides a composite view of the arbitrator with regard to the cluster's data nodes. If it has more than 1 row for longer than a few moments, then either not all nodes are connected to the arbitrator, or all ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cluster-locks.html
If a transaction holds an exclusive lock on a given row, all other locks on that row have the same transaction ID. The cluster_locks table provides information about current lock requests holding and waiting for locks on NDB tables in an NDB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cluster-operations.html
The state column can have any one of the values ABORT_QUEUED, ABORT_STOPPED, COMMITTED, COMMIT_QUEUED, COMMIT_STOPPED, COPY_CLOSE_STOPPED, COPY_FIRST_STOPPED, COPY_STOPPED, COPY_TUPKEY, IDLE, LOG_ABORT_QUEUED, LOG_COMMIT_QUEUED, ... The ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cluster-transactions.html
The state column can have any one of the values CS_ABORTING, CS_COMMITTING, CS_COMMIT_SENT, CS_COMPLETE_SENT, CS_COMPLETING, CS_CONNECTED, CS_DISCONNECTED, CS_FAIL_ABORTED, CS_FAIL_ABORTING, CS_FAIL_COMMITTED, CS_FAIL_COMMITTING, CS_FAIL_COMPLETED, ... The cluster_transactions table shows information about all ongoing transactions in an NDB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-counters.html
The counters table provides running totals of events such as reads and writes for specific kernel blocks and data nodes. Counts are kept from the most recent node start or restart; a node start or restart resets all counters on that node. The ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cpudata-1sec.html
The cpudata_1sec table provides data about CPU usage per second over the last 20 seconds.