Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-install-windows-service.html
Once you are satisfied that NDB Cluster is running as desired, you can install the management nodes and data nodes as Windows services, so that these processes are started and stopped automatically whenever Windows is started or stopped. This also ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-interconnects.html
Even before design of NDBCLUSTER began in 1996, it was evident that one of the major problems to be encountered in building parallel databases would be communication between the nodes in the network. For this reason, NDBCLUSTER was designed from ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-database-objects.html
Some database objects such as tables and indexes have different limitations when using the NDBCLUSTER storage engine: Number of database objects. The maximum number of all NDB database objects in a single NDB Cluster—including databases, tables, ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-disk-data.html
Disk data objects are subject to the following maximums and minimums: Maximum number of tablespaces: 232 (4294967296) Maximum number of data files per tablespace: 216 (65536) The minimum and maximum possible sizes of extents for tablespace data ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-exclusive-to-cluster.html
The following are limitations specific to the NDB storage engine: Machine architecture. All machines used in the cluster must have the same architecture. That is, all machines hosting nodes must be either big-endian or little-endian, and you cannot ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-performance.html
The following performance issues are specific to or especially pronounced in NDB Cluster: Range scans. There are query performance issues due to sequential access to the NDB storage engine; it is also relatively more expensive to do many range ...
https://dev.mysql.com/doc/refman/8.4/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/8.4/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.4/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.4/en/mysql-cluster-ndbinfo-blocks.html
The blocks table is a static table which simply contains the names and internal IDs of all NDB kernel blocks (see NDB Kernel Blocks). It is for use by the other ndbinfo tables (most of which are actually views) in mapping block numbers to block ...