NDB Cluster Configuration Files to 100 MB, and a given data node is using 50 MB for data memory storage, the corresponding line in the cluster log might look like this: MemReportFrequency  is not a required parameter. If used, it can be set for all cluster data nodes in the  [ndbd default]  section of  config.ini , and can also be set or overridden for individual data nodes in the corresponding  [ndbd]  sections of the configuration file. The minimum value—which is also the default value—is 0, in which case memory reports are logged only when memory usage reaches certain percentages (80%, 90%, and 100%), as mentioned in the discussion of statistics events in Section 23.5.3.2, “NDB Cluster Log Events” . 2006-12-24 01:18:16 [MgmSrvr] INFO -- Node 2: Data usage is 50%(1280 32K pages of total 2560) • StartupStatusReportFrequency Version (or later) NDB 8.0.13 Type or units seconds Default 0 Range 0 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) When a data node is started with the  --initial , it initializes the redo log file during Start Phase 4 (see Section 23.5.4, “Summary of NDB Cluster Start Phases” ). When very large values are set for  NoOfFragmentLogFiles ,  FragmentLogFileSize , or both, this initialization can take a long time.You can force reports on the progress of this process to be logged periodically, by means of the StartupStatusReportFrequency  configuration parameter. In this case, progress is reported in the cluster log, in terms of both the number of files and the amount of space that have been initialized, as shown here: These reports are logged each  StartupStatusReportFrequency  seconds during Start Phase 4. If StartupStatusReportFrequency  is 0 (the default), then reports are written to the cluster log only when at the beginning and at the completion of the redo log file initialization process. 2009-06-20 16:39:23 [MgmSrvr] INFO -- Node 1: Local redo log file initialization status: #Total files: 80, Completed: 60 #Total MBytes: 20480, Completed: 15557 2009-06-20 16:39:23 [MgmSrvr] INFO -- Node 2: Local redo log file initialization status: #Total files: 80, Completed: 60 #Total MBytes: 20480, Completed: 15570 The following parameters are intended for use during testing or debugging of data nodes, and not for use in production. • DictTrace Data Node Debugging Parameters Version (or later) NDB 8.0.13 Type or units bytes Default undefined Range 0 - 100 Restart Type N (NDB 8.0.13) It is possible to cause logging of traces for events generated by creating and dropping tables using DictTrace . This parameter is useful only in debugging NDB kernel code.  DictTrace  takes an integer 4119