MySQL 8.0 FAQ: NDB Cluster It is acceptable to run multiple cluster data nodes on a single host that has multiple CPUs, cores, or both. The NDB Cluster distribution also provides a multithreaded version of the data node binary intended for use on such systems. For more information, see Section 23.4.3, “ndbmtd — The NDB Cluster Data Node Daemon (Multi-Threaded)” . It is also possible in some cases to run data nodes and SQL nodes concurrently on the same machine; how well such an arrangement performs is dependent on a number of factors such as number of cores and CPUs as well as the amount of disk and memory available to the data node and SQL node processes, and you must take these factors into account when planning such a configuration. It is possible to add new data nodes to a running NDB Cluster without taking the cluster offline. For more information, see Section 23.5.7, “Adding NDB Cluster Data Nodes Online” . For other types of NDB Cluster nodes, a rolling restart is all that is required (see Section 23.5.5, “Performing a Rolling Restart of an NDB Cluster” ). Limitations on  NDB  tables in MySQL NDB Cluster include the following: There is no set limit for the number of rows per  NDB  table. Limits on table size depend on a number of factors, in particular on the amount of RAM available to each data node. For a complete listing of limitations in NDB Cluster, see Section 23.1.7, “Known Limitations of NDB Cluster” . See also Section 23.1.7.11, “Previous NDB Cluster Issues Resolved in NDB Cluster 8.0” . NDB Cluster provides support for foreign key constraints which is comparable to that found in the  InnoDB  storage engine; see Section 1.7.3.2, “FOREIGN KEY Constraints” , for more detailed 5253 A.10.26. Does NDB Cluster support foreign keys? A.10.25. Are there any limitations that I should be aware of when using NDB Cluster? A.10.24. Can I add data nodes to an NDB Cluster without restarting it? •Temporary tables are not supported; a  CREATE TEMPORARY TABLE  statement using ENGINE=NDB  or  ENGINE=NDBCLUSTER  fails with an error. •The only types of user-defined partitioning supported for  NDBCLUSTER  tables are  KEY  and LINEAR KEY . Trying to create an  NDB  table using any other partitioning type fails with an error. • FULLTEXT  indexes are not supported. •Index prefixes are not supported. Only complete columns may be indexed. •Spatial indexes are not supported (although spatial columns can be used). See Section 11.4, “Spatial Data Types” . •Support for partial transactions and partial rollbacks is comparable to that of other transactional storage engines such as  InnoDB  that can roll back individual statements. •The maximum number of attributes allowed per table is 512. Attribute names cannot be any longer than 31 characters. For each table, the maximum combined length of the table and database names is 122 characters. •Priot to NDB 8.0, the maximum size for a table row is 14 kilobytes, not counting  BLOB  values. In NDB 8.0, this maximum is increased to 30000 bytes. See Section 23.1.7.5, “Limits Associated with Database Objects in NDB Cluster” , for more information.