MySQL 8.0 FAQ: NDB Cluster NDB Cluster is supported for use in virtual machines. We currently support and test using Oracle VM. Some NDB Cluster users have successfully deployed NDB Cluster using other virtualization products; in such cases, Oracle can provide NDB Cluster support, but issues specific to the virtual environment must be referred to that product’s vendor. ERROR 1114: The table ’my_cluster_table’ is full Why is this happening? The cause is very likely to be that your setup does not provide sufficient RAM for all table data and all indexes,  including the primary key required by the  NDB  storage engine and automatically created in the event that the table definition does not include the definition of a primary key . It is also worth noting that all data nodes should have the same amount of RAM, since no data node in a cluster can use more memory than the least amount available to any individual data node. For example, if there are four computers hosting Cluster data nodes, and three of these have 3GB of RAM available to store Cluster data while the remaining data node has only 1GB RAM, then each data node can devote at most 1GB to NDB Cluster data and indexes. In some cases it is possible to get  Table is full  errors in MySQL client applications even when ndb_mgm -e "ALL REPORT MEMORYUSAGE"  shows significant free  DataMemory . You can force NDB  to create extra partitions for NDB Cluster tables and thus have more memory available for hash indexes by using the  MAX_ROWS  option for  CREATE TABLE . In general, setting  MAX_ROWS  to twice the number of rows that you expect to store in the table should be sufficient. For similar reasons, you can also sometimes encounter problems with data node restarts on nodes that are heavily loaded with data. The  MinFreePct  parameter can help with this issue by reserving a portion (5% by default) of  DataMemory  and (prior to NDB 7.6)  IndexMemory  for use in restarts. This reserved memory is not available for storing  NDB  tables or data. It is  very  unlikely that a cluster would perform reliably under such conditions, as NDB Cluster was designed and implemented with the assumption that it would be run under conditions guaranteeing dedicated high-speed connectivity such as that found in a LAN setting using 100 Mbps or gigabit Ethernet—preferably the latter. We neither test nor warrant its performance using anything slower than this. Also, it is extremely important to keep in mind that communications between the nodes in an NDB Cluster are not secure; they are neither encrypted nor safeguarded by any other protective mechanism. The most secure configuration for a cluster is in a private network behind a firewall, with no direct access to any Cluster data or management nodes from outside. (For SQL nodes, you should take the same precautions as you would with any other instance of the MySQL server.) For more information, see Section 23.5.17, “NDB Cluster Security Issues” . No . Although some specialized commands are used to manage and configure the cluster itself, only standard (My)SQL statements are required for the following operations: •Creating, altering, and dropping tables A.10.13. I am trying to populate an NDB Cluster database. The loading process terminates prematurely and I get an error message like this one: A.10.14. NDB Cluster uses TCP/IP. Does this mean that I can run it over the Internet, with one or more nodes in remote locations? A.10.15. Do I have to learn a new programming or query language to use NDB Cluster? 5250