NDB Cluster Configuration Files Setting this parameter enables you to control directly the size of redo log files. This can be useful in situations when NDB Cluster is operating under a high load and it is unable to close fragment log files quickly enough before attempting to open new ones (only 2 fragment log files can be open at one time); increasing the size of the fragment log files gives the cluster more time before having to open each new fragment log file. The default value for this parameter is 16M. For more information about fragment log files, see the description for  NoOfFragmentLogFiles . • InitialNoOfOpenFiles • InitFragmentLogFiles • SPARSE . Fragment log files are created sparsely. This is the default value. • FULL . Force all bytes of the fragment log file to be written to disk. • EnablePartialLcp Version (or later) NDB 8.0.13 Type or units boolean Default true Range ... 4090 Depending on your operating system and file system, setting  InitFragmentLogFiles=FULL  may help eliminate I/O errors on writes to the REDO log. By default, fragment log files are created sparsely when performing an initial start of a data node—that is, depending on the operating system and file system in use, not all bytes are necessarily written to disk. However, it is possible to override this behavior and force all bytes to be written, regardless of the platform and file system type being used, by means of this parameter.  InitFragmentLogFiles  takes either of two values: Version (or later) NDB 8.0.13 Type or units [see values] Default SPARSE Range SPARSE, FULL Restart Type IN (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units files Default 27 Range 20 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) This parameter sets the initial number of internal threads to allocate for open files. The default value is 27.