Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-backup-using-management-client.html
Before starting a backup, make sure that the cluster is properly configured for performing one. If an existing backup_id value is used, the backup fails with the error Backup failed: file already exists. If used, the backup_id must follow ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-backup.html
To distinguish this type of backup from a backup made using mysqldump, we sometimes refer to it as a “native” NDB Cluster backup. The next few sections describe how to prepare for and then to create an NDB Cluster backup using the functionality ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-computer-definition.html
The [computer] section has no real significance other than serving as a way to avoid the need of defining host names for each node in the system. Id Version (or later) NDB 8.4.0 Type or units string Default [...] Range ... Restart Type Initial ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-configuration-overview.html
Each of the node parameter tables lists the parameters for a given type (ndbd, ndb_mgmd, mysqld, computer, tcp, or shm). All tables include the data type for the parameter, option, or variable, as well as its default, minimum, and maximum values as ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-disk-data-storage-requirements.html
The following items apply to Disk Data storage requirements: Variable-length columns of Disk Data tables take up a fixed amount of space. For each row, this is equal to the space required to store the largest possible value for that column. For ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-disk-data.html
NDB Cluster supports storing nonindexed columns of NDB tables on disk, rather than in RAM. Column data and logging metadata are kept in data files and undo log files, conceptualized as tablespaces and log file groups, as described in the next ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-information-schema-tables.html
The ndb_transid_mysql_connection_map table provides a mapping between transactions, transaction coordinators, and API nodes. Two INFORMATION_SCHEMA tables provide information that is of particular use when managing an NDB Cluster. The FILES table ...
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-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 ...