NDB Cluster Configuration Files do not meet. When these approach one another too closely, the node begins aborting all transactions encompassing updates due to a lack of room for new log records. A  REDO  log record is not removed until both required local checkpoints have been completed since that log record was inserted. Checkpointing frequency is determined by its own set of configuration parameters discussed elsewhere in this chapter. The default parameter value is 16, which by default means 16 sets of 4 16MB files for a total of 1024MB. The size of the individual log files is configurable using the  FragmentLogFileSize  parameter. In scenarios requiring a great many updates, the value for  NoOfFragmentLogFiles  may need to be set as high as 300 or even higher to provide sufficient space for REDO logs. If the checkpointing is slow and there are so many writes to the database that the log files are full and the log tail cannot be cut without jeopardizing recovery, all updating transactions are aborted with internal error code 410 ( Out of log file space temporarily ). This condition prevails until a checkpoint has completed and the log tail can be moved forward. This parameter cannot be changed “on the fly” ; you must restart the node using --initial . If you wish to change this value for all data nodes in a running cluster, you can do so using a rolling node restart (using  --initial  when starting each data node). Important • RecoveryWork •Fewer records are written for each LCP, LCPs use more space •More work is needed during restarts A lower value for  RecoveryWork  means: •More records are written during each LCP, but LCPs require less space on disk. •Less work during restart and thus faster restarts, at the expense of more work during normal operations 4093 For example, setting  RecoveryWork  to 60 means that the total size of an LCP is roughly 1 + 0.6 = 1.6 times the size of the data to be checkpointed. This means that 60% more work is required during the restore phase of a restart compared to the work done during a restart that uses full checkpoints. (This is more than compensated for during other phases of the restart such that the restart as a whole is still faster when using partial LCPs than when using full LCPs.) In order not to fill up the redo log, it is necessary to write at 1 + (1 /  RecoveryWork ) times the rate of data changes during checkpoints— thus, when  RecoveryWork  = 60, it is necessary to write at approximately 1 + (1 / 0.6 ) = 2.67 times the Percentage of storage overhead for LCP files. This parameter has an effect only when EnablePartialLcp  is true, that is, only when partial local checkpoints are enabled. A higher value means: Version (or later) NDB 8.0.13 Type or units integer Default 60 Range 25 - 100 Restart Type N (NDB 8.0.13)