NDB Cluster Configuration Files Range 0, 1 Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units boolean Default false Range true, false Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units milliseconds Default 6000 Range 70 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 4102 • TimeBetweenWatchDogCheckInitial The default timeout is 6000 milliseconds (6 seconds). This parameter can easily be changed for purposes of experimentation or to adapt to local conditions. It can be specified on a per-node basis although there seems to be little reason for doing so. To prevent the main thread from getting stuck in an endless loop at some point, a “watchdog”  thread checks the main thread. This parameter specifies the number of milliseconds between checks. If the process remains in the same state after three checks, the watchdog thread terminates it. • TimeBetweenWatchDogCheck • UseShm This parameter specifies whether a data node process should exit or perform an automatic restart when an error condition is encountered. This parameter’s default value is 1; this means that, by default, an error causes the data node process to halt. When an error is encountered and  StopOnError  is 0, the data node process is restarted. Users of MySQL Cluster Manager should note that, when  StopOnError  equals 1, this prevents the MySQL Cluster Manager agent from restarting any data nodes after it has performed its own restart and recovery. See Starting and Stopping the Agent on Linux, for more information. Enable a shared memory connection between this data node and the API node also running on this host. Set to 1 to enable. There are a number of  [ndbd]  parameters specifying timeouts and intervals between various actions in Cluster data nodes. Most of the timeout values are specified in milliseconds. Any exceptions to this are mentioned where applicable. Controlling Timeouts, Intervals, and Disk Paging