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-transactions.html
As noted elsewhere in this chapter, NDB Cluster does not handle large transactions well; it is better to perform a number of small transactions with a few operations each than to attempt a single large transaction containing a great many operations.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-unsupported.html
Note See Section 25.2.7.3, “Limits Relating to Transaction Handling in NDB Cluster”, for more information relating to limitations on transaction handling in NDB. A number of features supported by other storage engines are not supported for NDB ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations.html
Note Limitations and other issues specific to NDB Cluster Replication are described in Section 25.7.3, “Known Issues in NDB Cluster Replication”. In the sections that follow, we discuss known limitations in current releases of NDB Cluster as ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-log-events.html
An event report reported in the event logs has the following format: datetime [string] severity -- message For example: 09:19:30 2005-07-24 [NDB] INFO -- Node 4 Start phase 4 completed This section discusses all reportable events, ordered by ...
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-ndb-transporter-errors.html
This section lists error codes, names, and messages that are written to the cluster log in the event of transporter errors. 0x00 TE_NO_ERROR No error 0x01 TE_ERROR_CLOSING_SOCKET Error found during closing of socket 0x02 ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-arbitrator-validity-detail.html
The arbitrator_validity_detail table shows the view that each data node in the cluster has of the arbitrator. All nodes should show the same arbitrator and arb_ticket values as well as the same arb_state value. Possible arb_state values are ...
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-blocks.html
The blocks table contains the following columns: block_number Block number block_name Block name Notes To obtain a list of all block names, simply execute SELECT block_name FROM ndbinfo.blocks. The blocks table is a static table which simply ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cluster-locks.html
The cluster_locks table provides information about current lock requests holding and waiting for locks on NDB tables in an NDB Cluster, and is intended as a companion table to cluster_operations. Information obtain from the cluster_locks table may ...