NDB Cluster Configuration Files This is similar to the  TimeBetweenWatchDogCheck  parameter, except that TimeBetweenWatchDogCheckInitial  controls the amount of time that passes between execution checks inside a storage node in the early start phases during which memory is allocated. The default timeout is 6000 milliseconds (6 seconds). This parameter specifies how long the Cluster waits for all data nodes to come up before the cluster initialization routine is invoked. This timeout is used to avoid a partial Cluster startup whenever possible. This parameter is overridden when performing an initial start or initial restart of the cluster. The default value is 30000 milliseconds (30 seconds). 0 disables the timeout, in which case the cluster may start only if all nodes are available. If the cluster is ready to start after waiting for  StartPartialTimeout  milliseconds but is still possibly in a partitioned state, the cluster waits until this timeout has also passed. If StartPartitionedTimeout  is set to 0, the cluster waits indefinitely (2 32 − 1 ms, or approximately 49.71 days). This parameter is overridden when performing an initial start or initial restart of the cluster. • StartFailureTimeout • StartPartitionedTimeout • StartPartialTimeout Type or units milliseconds Default 6000 Range 70 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units milliseconds Default 30000 Range 0 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units milliseconds Default 0 Range 0 - 4294967039 (0xFFFFFEFF) Restart Type N (NDB 8.0.13) Version (or later) NDB 8.0.13 Type or units milliseconds Default 0 Range 0 - 4294967039 (0xFFFFFEFF) 4103