content_image/791850.jpg
not specified, then FileSystemPathDD  is used (or FileSystemPath , if FileSystemPathDD  has also not been set). 

If a FileSystemPathUndoFiles  directory is specified for a given data node (including the case where the parameter is specified in the [ndbd default]  section of the config.ini  file), then starting that data node with --initial  causes all files in the directory to be deleted. 

For more information, see Section 23.5.10.1, “NDB Cluster Disk Data Objects” . 

• Disk Data object creation parameters.  The next two parameters enable you—when starting the cluster for the first time—to cause a Disk Data log file group, tablespace, or both, to be created without the use of SQL statements. 

• InitialLogFileGroup 

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

This parameter can be used to specify a log file group that is created when performing an initial start of the cluster. InitialLogFileGroup  is specified as shown here: 

InitialLogFileGroup = [name= name ;] [undo_buffer_size= size ;] file-specification-list file-specification-list : file-specification [; file-specification [; ...]] file-specification : filename : size 

The name  of the log file group is optional and defaults to DEFAULT-LG . The undo_buffer_size is also optional; if omitted, it defaults to 64M . Each file-specification  corresponds to an undo log file, and at least one must be specified in the file-specification-list . Undo log files are placed according to any values that have been set for FileSystemPath , FileSystemPathDD , and FileSystemPathUndoFiles , just as if they had been created as the result of a CREATE LOGFILE GROUP  or ALTER LOGFILE GROUP  statement. 

Consider the following: 

InitialLogFileGroup = name=LG1; undo_buffer_size=128M; undo1.log:250M; undo2.log:150M 

This is equivalent to the following SQL statements: 

CREATE LOGFILE GROUP LG1 ADD UNDOFILE ’undo1.log’ INITIAL_SIZE 250M UNDO_BUFFER_SIZE 128M ENGINE NDBCLUSTER; ALTER LOGFILE GROUP LG1 ADD UNDOFILE ’undo2.log’ INITIAL_SIZE 150M 

