NDB Cluster Configuration Files • The management server is started using the --reload option.   The  --reload  option causes the management server to compare its cache with the global configuration file. If they differ, the management server creates a new configuration cache; any existing configuration cache is preserved, but not used. If the management server’s cache and the global configuration file contain the same configuration data, then the existing cache is used, and no new cache is created. • The management server is started using --config-cache=FALSE.   This disables  --config- cache  (enabled by default), and can be used to force the management server to bypass configuration caching altogether. In this case, the management server ignores any configuration files that may be present, always reading its configuration data from the  config.ini  file instead. • No configuration cache is found.   In this case, the management server reads the global configuration file and creates a cache containing the same configuration data as found in the file. Configuration cache files.   The management server by default creates configuration cache files in a directory named  mysql-cluster  in the MySQL installation directory. (If you build NDB Cluster from source on a Unix system, the default location is  /usr/local/mysql-cluster .) This can be overridden at runtime by starting the management server with the  --configdir  option. Configuration cache files are binary files named according to the pattern  ndb_ node_id _config.bin. seq_id , where  node_id  is the management server’s node ID in the cluster, and  seq_id  is a cache idenitifer. Cache files are numbered sequentially using  seq_id , in the order in which they are created. The management server uses the latest cache file as determined by the  seq_id . It is possible to roll back to a previous configuration by deleting later configuration cache files, or by renaming an earlier cache file so that it has a higher  seq_id . However, since configuration cache files are written in a binary format, you should not attempt to edit their contents by hand. For more information about the  --configdir ,  --config-cache ,  --initial , and  --reload options for the NDB Cluster management server, see Section 23.4.4, “ndb_mgmd — The NDB Cluster Management Server Daemon” . We are continuously making improvements in NDB 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 try to let NDB 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.6, “How to Report Bugs or Problems” . To support NDB Cluster, you should update  my.cnf  as shown in the following example. You may also specify these parameters on the command line when invoking the executables. The options shown here should not be confused with those that are used in config.ini  global configuration files. Global configuration options are discussed later in this section. # my.cnf # example additions to my.cnf for NDB Cluster # (valid in MySQL 8.0) # enable ndbcluster storage engine, and provide connection string for # management server host (default port is 1186) 4053 23.3.3.1 NDB Cluster Configuration: Basic Example Note Note