The following table provides information about parameters used
in the [ndbd] or [ndbd
default] sections of a config.ini
file for configuring MySQL Cluster data nodes. For detailed
descriptions and other additional information about each of
these parameters, see
Section 15.3.2.5, “Defining MySQL Cluster Data Nodes”.
Table 15.1. Data Node Configuration Parameters
| Name | Type/Units | Default | Min Value | Max Value | Restart Type |
|---|---|---|---|---|---|
| ArbitrationTimeout | milliseconds | 1000 | 10 | 4G | N |
| BackupDataBufferSize | bytes | 2M | 4G | N | |
| BackupDataDir | path | FileSystemPath/BACKUP | IN | ||
| BackupLogBufferSize | bytes | 2M | 4G | N | |
| BackupMaxWriteSize | bytes | 256K | 2K | 4G | N |
| BackupMemory | bytes | 4M | 4G | N | |
| BackupWriteSize | bytes | 32K | 2K | 4G | N |
| BatchSizePerLocalScan | integer | 64 | 1 | 992 | N |
| DataDir | path | . | IN | ||
| DataMemory | bytes | 80M | 1M | 1024G | N |
| Diskless | true|false (1|0) | 1 | IS | ||
| ExecuteOnComputer | name | S | |||
| HeartbeatIntervalDbApi | milliseconds | 1500 | 100 | 4G | N |
| HeartbeatIntervalDbDb | milliseconds | 1500 | 10 | 4G | N |
| HostName | name or IP | localhost | IN | ||
| Id | unsigned | 1 | 48 | N | |
| IndexMemory | bytes | 18M | 1M | 1T | N |
| LockPagesInMainMemory | true|false (1|0) | 1 | N | ||
| LogLevelCheckpoint | log level | 15 | IN | ||
| LogLevelConnection | integer | 15 | N | ||
| LogLevelError | integer | 15 | N | ||
| LogLevelInfo | integer | 15 | N | ||
| LogLevelNodeRestart | integer | 15 | N | ||
| LogLevelShutdown | integer | 15 | N | ||
| LogLevelStartup | integer | 1 | 15 | N | |
| LogLevelStatistic | integer | 15 | N | ||
| LongMessageBuffer | N | ||||
| MaxNoOfAttributes | integer | 1000 | 32 | 4G | N |
| MaxNoOfConcurrentIndexOperations | integer | 8K | 4G | N | |
| MaxNoOfConcurrentOperations | integer | 32K | 32 | 4G | N |
| MaxNoOfConcurrentScans | integer | 256 | 2 | 500 | N |
| MaxNoOfConcurrentTransactions | integer | 4096 | 32 | 4G | S |
| MaxNoOfFiredTriggers | integer | 4000 | 4G | N | |
| MaxNoOfLocalOperations | integer | UNDEFINED | 32 | 4G | N |
| MaxNoOfLocalScans | integer | UNDEFINED | 32 | 4G | N |
| MaxNoOfOpenFiles | N | ||||
| MaxNoOfOrderedIndexes | integer | 128 | 4G | N | |
| MaxNoOfSavedMessages | integer | 25 | 4G | N | |
| MaxNoOfTables | integer | 128 | 8 | 1600 | N |
| MaxNoOfTriggers | integer | 768 | 4G | N | |
| MaxNoOfUniqueHashIndexes | integer | 64 | 4G | N | |
| NoOfDiskPagesToDiskAfterRestartACC | N | ||||
| NoOfDiskPagesToDiskAfterRestartTUP | N | ||||
| NoOfDiskPagesToDiskDuringRestartACC | N | ||||
| NoOfDiskPagesToDiskDuringRestartTUP | N | ||||
| NoOfFragmentLogFiles | integer | 8 | 3 | 4G | IN |
| NoOfReplicas | IS | ||||
| RedoBuffer | bytes | 8M | 1M | 4G | N |
| RestartOnErrorInsert | error code | 2 | 4 | N | |
| ServerPort | unsigned | 1 | 64K | N | |
| StartFailureTimeout | milliseconds | 4G | N | ||
| StartPartialTimeout | milliseconds | 30000 | 4G | N | |
| StartPartitionedTimeout | milliseconds | 60000 | 4G | N | |
| StopOnError | true|false (1|0) | true | N | ||
| StringMemory | % or bytes | 4G | S | ||
| TimeBetweenGlobalCheckpoints | milliseconds | 2000 | 10 | 32000 | N |
| TimeBetweenInactiveTransactionAbortCheck | milliseconds | 1000 | 1000 | 4G | N |
| TimeBetweenLocalCheckpoints | number of 4-byte words, as a base-2 logarithm | 20 | 31 | N | |
| TimeBetweenWatchDogCheck | milliseconds | 6000 | 70 | 4G | N |
| TransactionBufferMemory | bytes | 1M | 1K | 4G | N |
| TransactionDeadlockDetectionTimeout | milliseconds | 1200 | 50 | 4G | N |
| TransactionInactiveTimeout | milliseconds | 4G | 4G | N | |
| UndoDataBuffer | unsigned | 16M | 1M | 4G | N |
| UndoIndexBuffer | unsigned | 2M | 1M | 4G | N |
To add new data nodes to a MySQL Cluster, it is necessary to
shut down the cluster completely, update the
config.ini file, and then restart the
cluster (that is, you must perform a system restart). All data
node processes must be started with the
--initial option.
We are working to make it possible to add new data node groups to a running cluster online in a future release; however, we do not plan to implement this change in MySQL 4.1.


User Comments
Add your own comment.