NDB Cluster Configuration Files • ndb_use_transactions : Forces NDB to use a count of records during SELECT COUNT(*) query planning to speed up this type of query. • ndb_version : Shows build and NDB engine version as an integer. • ndb_version_string : Shows build information including NDB engine version in ndb-x.y.z format. • ndbcluster : Enable NDB Cluster (if this version of MySQL supports it). Disabled by  --skip- ndbcluster . • ndbinfo : Enable ndbinfo plugin, if supported. • ndbinfo_database : Name used for NDB information database; read only. • ndbinfo_max_bytes : Used for debugging only. • ndbinfo_max_rows : Used for debugging only. • ndbinfo_offline : Put ndbinfo database into offline mode, in which no rows are returned from tables or views. • ndbinfo_show_hidden : Whether to show ndbinfo internal base tables in mysql client; default is OFF. • ndbinfo_table_prefix : Prefix to use for naming ndbinfo internal base tables; read only. • ndbinfo_version : ndbinfo engine version; read only. • server_id_bits : Number of least significant bits in server_id actually used for identifying server, permitting NDB API applications to store application data in most significant bits. server_id must be less than 2 to power of this value. • skip-ndbcluster : Disable NDB Cluster storage engine. • slave_allow_batching : Turns update batching on and off for replica. • transaction_allow_batching : Allows batching of statements within one transaction. Disable AUTOCOMMIT to use. 23.3.3 NDB Cluster Configuration Files Configuring NDB Cluster requires working with two files: • my.cnf : Specifies options for all NDB 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 NDB 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. • The management server is started using the --initial option.   When  --initial  is used, the global configuration file is re-read, any existing cache files are deleted, and the management server creates a new configuration cache. Caching of configuration data.  NDB  uses  stateful configuration . Rather than reading the global configuration file every time the management server is restarted, the management server caches the configuration the first time it is started, and thereafter, the global configuration file is read only when one of the following conditions is true: 4052