Skip navigation links
MySQL 5.0 Reference Manual :: 17 MySQL Cluster :: 17.3 MySQL Cluster Configuration :: 17.3.2 MySQL Cluster Configuration Files
17.3.2.1 MySQL Cluster Configuration — Basic Example »
Section Navigation      [Toggle]

17.3.2. MySQL Cluster Configuration Files

[+/-]

17.3.2.1. MySQL Cluster Configuration — Basic Example
17.3.2.2. The MySQL Cluster Connectstring
17.3.2.3. Defining Computers in a MySQL Cluster
17.3.2.4. Defining a MySQL Cluster Management Server
17.3.2.5. Defining MySQL Cluster Data Nodes
17.3.2.6. Defining SQL and Other API Nodes in a MySQL Cluster
17.3.2.7. MySQL Cluster TCP/IP Connections
17.3.2.8. MySQL Cluster TCP/IP Connections Using Direct Connections
17.3.2.9. MySQL Cluster Shared-Memory Connections
17.3.2.10. SCI Transport Connections in MySQL Cluster
17.3.2.11. Configuring MySQL Cluster Parameters for Local Checkpoints

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. config.ini contains a description of each node involved 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 Sections of the config.ini File.

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 backward compatible. If you find such a change and we have not documented it, please report it in the MySQL bugs database using the instructions given in Section 1.7, “How to Report Bugs or Problems”.