Oracle 5.0 Reference Manual page 1598

RedoBuffer
Effective Version
MySQL 5.0.0
Restart Type: N
All update activities also need to be logged. The REDO log makes it possible to replay these updates
whenever the system is restarted. The NDB recovery algorithm uses a "fuzzy" checkpoint of the
data together with the UNDO log, and then applies the REDO log to play back all changes up to the
restoration point.
sets the size of the buffer in which the REDO log is written, and is 8MB by default. The
RedoBuffer
minimum value is 1MB.
If this buffer is too small, the NDB storage engine issues error code 1221
overloaded).
Important
It is not safe to decrease the value of this parameter during a rolling restart.
Controlling log messages.
number of log messages sent for various event types to stdout. For each event category, there are
16 possible event levels (numbered 0 through 15). Setting event reporting for a given event category
to level 15 means all event reports in that category are sent to stdout; setting it to 0 means that there
will be no event reports made in that category.
By default, only the startup message is sent to stdout, with the remaining event reporting level
defaults being set to 0. The reason for this is that these messages are also sent to the management
server's cluster log.
An analogous set of levels can be set for the management client to determine which event levels to
record in the cluster log.
•
LogLevelStartup
Effective Version
MySQL 5.0.0
Restart Type: N
The reporting level for events generated during startup of the process.
The default level is 1.
•
LogLevelShutdown
Effective Version
MySQL 5.0.0
Restart Type: N
The reporting level for events generated as part of graceful shutdown of a node.
The default level is 0.
•
MySQL Cluster Configuration Files
Type/Units
bytes
In managing the cluster, it is very important to be able to control the
Type/Units
integer
Type/Units
integer
1578
Default
8M
(REDO log buffers
Default
1
Default
0
Range/Values
1M - 4G
Range/Values
0 - 15
Range/Values
0 - 15