Mysql Cluster Configuration Files - Oracle 5.0 Reference Manual

...
The row numbers shown in the preceding example output may be different from those shown on your
system, depending upon how your server is configured.
Try to create an
shell> mysql
mysql> USE test;
Database changed
mysql> CREATE TABLE ctest (i INT) ENGINE=NDBCLUSTER;
Query OK, 0 rows affected (0.09 sec)
mysql> SHOW CREATE TABLE ctest \G
*************************** 1. row ***************************
Table: ctest
Create Table: CREATE TABLE `ctest` (
`i` int(11) default NULL
) ENGINE=ndbcluster DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
To check that your nodes were set up properly, start the management client:
shell> ndb_mgm
Use the
SHOW
ndb_mgm> SHOW
Cluster Configuration
---------------------
[ndbd(NDB)]
id=2 @127.0.0.1
[ndb_mgmd(MGM)] 1 node(s)
id=1 @127.0.0.1
[mysqld(API)]
id=3 @127.0.0.1
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)
At this point, you have successfully set up a working MySQL Cluster. You can now store data in the
cluster by using any table created with

17.3.2. MySQL Cluster Configuration Files

Configuring MySQL Cluster requires working with two files:
• my.cnf: Specifies options for all MySQL Cluster executables. This file, with which you should be
familiar with from previous work with MySQL, must be accessible by each executable running in the
cluster.
• config.ini: This file, sometimes known as the global configuration file, is read only by the MySQL
Cluster management server, which then distributes the information contained therein to all processes
participating in the cluster.
This includes configuration parameters for data nodes and configuration parameters for connections
between all nodes in the cluster. For a quick reference to the sections that can appear in this file,
and what sorts of configuration parameters may be placed in each section, see
config.ini
We are continuously making improvements in Cluster configuration and attempting to simplify this
process. Although we strive to maintain backward compatibility, there may be times when introduce an
incompatible change. In such cases we will try to let Cluster users know in advance if a change is not
MySQL Cluster Configuration Files
table:
NDBCLUSTER
command from within the management client to obtain a report on the cluster's status:
1 node(s)
(Version: 3.5.3, Nodegroup: 0, Master)
(Version: 3.5.3)
3 node(s)
(Version: 3.5.3)
config.ini
File [1550].
ENGINE=NDBCLUSTER
contains a description of each node involved in the cluster.
1548
or its alias ENGINE=NDB.
Sections of the