PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-limitations-limits.html
These hard limits include: Database memory size and index memory size (DataMemory and IndexMemory, respectively). In this section, we list limits found in NDB Cluster that either differ from limits found in, or that are not found in, standard MySQL. Memory consumed when data is inserted into an NDB table is not automatically recovered when deleted, as it is with other storage ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-limitations-transactions.html
See Section 21.6.8.4, “NDB Cluster Backup Troubleshooting”, for information on how NDB Cluster's implementation of transaction isolation level can affect backup and restoration of NDB databases. A number of limitations exist in NDB Cluster with ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-logging-management-commands.html
ndb_mgm supports a number of management commands related to the cluster log and node logs. In the listing that follows, node_id denotes either a storage node ID or the keyword ALL, which indicates that the command should be applied to all of the ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/en/mysql-cluster-ndb-innodb-workloads.html
A number of major differences in behavior between the NDB and InnoDB storage engines with regard to some common types of database-driven application workloads are shown in the following table:: Table 21.2 Differences between InnoDB and NDB storage ... NDB Cluster has a range of unique attributes that make it ideal to serve applications requiring high availability, fast failover, high throughput, and low ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-online-add-node-example.html
In this section we provide a detailed example illustrating how to add new NDB Cluster data nodes online, starting with an NDB Cluster having 2 data nodes in a single node group and concluding with a cluster having 4 data nodes in 2 node groups.
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-top.html
This user must be able to read tables in the ndbinfo database (ndb_top uses information from ndbinfo.cpustat and related tables). ndb_top displays running information in the terminal about CPU usage by NDB threads on an NDB Cluster data node. Each ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-quick.html
Try to create an NDBCLUSTER table: $> mysql mysql> USE test; Database changed mysql> CREATE TABLE ctest (i INT) ENGINE=NDBCLUSTER; Query OK, 0 rows affected (0.09 sec) mysql> SHOW CREATE TABLE ctest \G *************************** 1. To familiarize ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-general.html
Tables and other database objects created using the NDB API (with, for example, Dictionary::createTable()) are not visible to a MySQL server and so are not replicated. A replication channel requires two MySQL servers acting as replication servers ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-pitr.html
To perform point-in-time recovery of NDB Cluster, it is necessary to follow the steps shown here: Back up all NDB databases in the cluster, using the START BACKUP command in the ndb_mgm client (see Section 21.6.8, “Online Backup of NDB Cluster”). Point-in-time recovery—that is, recovery of data changes made since a given point in time—is performed after restoring a full backup that returns the server to its state when the backup was ...