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-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 25.3 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/8.0/en/mysql-cluster-overview-requirements.html
(It is possible to reduce this requirement using Disk Data tables—see Section 25.6.11, “NDB Cluster Disk Data Tables”, for more information about these.) Naturally, multiple and faster CPUs can enhance performance. Data node recovery requires ... One of the strengths of NDB Cluster is that it can be run on commodity hardware and has no unusual requirements in this regard, other than for large amounts of RAM, due to the fact that all live data storage is done in ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-print-file.html
For more information, see Section 25.6.11, “NDB Cluster Disk Data Tables”. ndb_print_file obtains information from an NDB Cluster Disk Data file. Usage ndb_print_file [-v] [-q] file_name+ file_name is the name of an NDB Cluster Disk Data file.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-print-frag-file.html
Each fragment file contains records of the fragments belonging to each NDB table. It is intended for use in helping to diagnose issues with data node restarts. For more information about cluster fragment files, see NDB Cluster Data Node File System ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-security-mysql-security-procedures.html
Alternatively, you can start the MySQL server process with --user=mysql on the command line, but it is preferable to use the my.cnf option, since you might forget to use the command-line option and so have mysqld running as another user ... In this ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-single-user-mode.html
You can also check the status column of the ndbinfo.nodes table (see Section 25.6.16.47, “The ndbinfo nodes Table”, for more information). Single user mode enables the database administrator to restrict access to the database system to a single ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-system-definition.html
The [system] section is used for parameters applying to the cluster as a whole. The Name system parameter is used with MySQL Enterprise Monitor; ConfigGenerationNumber and PrimaryMGMNode are not used in production environments. Except when using ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-tcp-definition.html
TCP/IP is the default transport mechanism for all connections between nodes in an NDB Cluster. Normally it is not necessary to define TCP/IP connections; NDB Cluster automatically sets up such connections for all data nodes, management nodes, and ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-tde-limitations.html
Replication of an NDB Cluster whose file system is encrypted to a standalone MySQL server using InnoDB tables which are not encrypted. Replication of an NDB Cluster with an unencrypted file system to a standalone MySQL server using InnoDB tables ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-thread-states.html
Processing events from schema table The thread is doing the work of schema replication. Shutting down Syncing ndb table schema operation and binlog This is used to have a correct binary log of schema operations for NDB. Committing events to binlog ...