NDB Cluster Configuration Files buffer can be adjusted as necessary. (Previously, the NDB kernel used a fixed-size send buffer for every node in the cluster, which was allocated when the node started and could not be changed while the node was running.) The  TotalSendBufferMemory  and  OverLoadLimit  data node configuration parameters permit the setting of limits on this memory allocation. For more information about the use of these parameters (as well as  SendBufferMemory ), see Section 23.3.3.14, “Configuring NDB Cluster Send Buffer Parameters” . This parameter specifies the amount of transporter send buffer memory to allocate in addition to any set using  TotalSendBufferMemory ,  SendBufferMemory , or both. This parameter is used to determine the total amount of memory to allocate on this node for shared send buffer memory among all configured transporters. If this parameter is set, its minimum permitted value is 256KB; 0 indicates that the parameter has not been set. For more detailed information, see Section 23.3.3.14, “Configuring NDB Cluster Send Buffer Parameters” . See also Section 23.5.7, “Adding NDB Cluster Data Nodes Online” . Redo log over-commit handling.   It is possible to control a data node’s handling of operations when too much time is taken flushing redo logs to disk. This occurs when a given redo log flush takes longer than  RedoOverCommitLimit  seconds, more than  RedoOverCommitCounter  times, causing any pending transactions to be aborted. When this happens, the API node that sent the transaction can handle the operations that should have been committed either by queuing the operations and re-trying them, or by aborting them, as determined by  DefaultOperationRedoProblemAction . The data node configuration parameters for setting the timeout and number of times it may be exceeded before the API node takes this action are described in the following list: When  RedoOverCommitLimit  is exceeded when trying to write a given redo log to disk this many times or more, any transactions that were not committed as a result are aborted, and an API node where any of these transactions originated handles the operations making up those transactions according to its value for  DefaultOperationRedoProblemAction  (by either queuing the operations to be re-tried, or aborting them). 4147 • RedoOverCommitLimit • RedoOverCommitCounter • TotalSendBufferMemory • ExtraSendBufferMemory Version (or later) NDB 8.0.13 Version (or later) NDB 8.0.13 Type or units numeric Default 3 Range 1 - 4294967039 (0xFFFFFEFF) Version (or later) NDB 8.0.19 Type or units numeric Default 3 Range 1 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13)