content_image/774034.jpg content_image/774033.jpg content_image/774032.jpg
<img src='content_image/774034.jpg'>

When true , enable partial local checkpoints: This means that each LCP records only part of the full database, plus any records containing rows changed since the last LCP; if no rows have changed, the LCP updates only the LCP control file and does not update any data files. 

If EnablePartialLcp  is disabled ( false ), each LCP uses only a single file and writes a full checkpoint; this requires the least amount of disk space for LCPs, but increases the write load for each LCP. The default value is enabled ( true ). The proportion of space used by partial LCPS can be modified by the setting for the RecoveryWork  configuration parameter. 

For more information about files and directories used for full and partial LCPs, see NDB Cluster Data Node File System Directory. 

Setting this parameter to false  also disables the calculation of disk write speed used by the adaptive LCP control mechanism. 

• LcpScanProgressTimeout 

<img src='content_image/774033.jpg'>

A local checkpoint fragment scan watchdog checks periodically for no progress in each fragment scan performed as part of a local checkpoint, and shuts down the node if there is no progress after a given amount of time has elapsed. This interval can be set using the LcpScanProgressTimeout  data node configuration parameter, which sets the maximum time for which the local checkpoint can be stalled before the LCP fragment scan watchdog shuts down the node. 

The default value is 60 seconds (providing compatibility with previous releases). Setting this parameter to 0 disables the LCP fragment scan watchdog altogether. 

• MaxNoOfOpenFiles 

<img src='content_image/774032.jpg'>

This parameter sets a ceiling on how many internal threads to allocate for open files. Any situation requiring a change in this parameter should be reported as a bug . 

The default value is 0. However, the minimum value to which this parameter can be set is 20. 

