18.2.5 Initial Startup of MySQL Cluster

Starting the cluster is not very difficult after it has been
configured. Each cluster node process must be started separately,
and on the host where it resides. The management node should be
started first, followed by the data nodes, and then finally by any
SQL nodes:

On the management host, issue the following command from the
system shell to start the management node process:

On each of the data node hosts, run this command to start the
ndbd process:

shell> ndbd

If you used RPM files to install MySQL on the cluster host
where the SQL node is to reside, you can (and should) use the
supplied startup script to start the MySQL server process on
the SQL node.

If all has gone well, and the cluster has been set up correctly,
the cluster should now be operational. You can test this by
invoking the ndb_mgm management node client.
The output should look like that shown here, although you might
see some slight differences in the output depending upon the exact
version of MySQL that you are using:

The SQL node is referenced here as
[mysqld(API)], which reflects the fact that the
mysqld process is acting as a MySQL Cluster API
node.

Note

The IP address shown for a given MySQL Cluster SQL or other API
node in the output of SHOW
is the address used by the SQL or API node to connect to the
cluster data nodes, and not to any management node.