A MySQL server that is part of an NDB Cluster differs in one chief
respect from a normal (nonclustered) MySQL server, in that it
NDB storage engine. This
engine is also referred to sometimes as
NDB is preferred.
To avoid unnecessary allocation of resources, the server is
configured by default with the
storage engine disabled. To enable
you must modify the server's
configuration file, or start the server with the
This MySQL server is a part of the cluster, so it also must know how
to access a management node to obtain the cluster configuration
data. The default behavior is to look for the management node on
localhost. However, should you need to specify
that its location is elsewhere, this can be done in
my.cnf, or with the mysql
client. Before the
NDB storage engine
can be used, at least one management node must be operational, as
well as any desired data nodes.
For more information about
--ndbcluster and other
mysqld options specific to NDB Cluster, see
Section 220.127.116.11.1, “MySQL Server Options for NDB Cluster”.
You can use also the NDB Cluster Auto-Installer to set up and deploy an NDB Cluster on one or more hosts using a browser-based GUI. For more information, see Section 21.2.1, “The NDB Cluster Auto-Installer”.
For general information about installing NDB Cluster, see Section 21.2, “NDB Cluster Installation”.