MySQL Cluster Configuration Files
1577
Effective Version
Type/Units
Default
Range/Values
Restart Type: N
The UNDO index buffer, whose size is set by this parameter, is used during local checkpoints. The
NDB
storage engine uses a recovery scheme based on checkpoint consistency in conjunction with
an operational REDO log. To produce a consistent checkpoint without blocking the entire system for
writes, UNDO logging is done while performing the local checkpoint. UNDO logging is activated on
a single table fragment at a time. This optimization is possible because tables are stored entirely in
main memory.
The UNDO index buffer is used for the updates on the primary key hash index. Inserts and deletes
rearrange the hash index; the NDB storage engine writes UNDO log records that map all physical
changes to an index page so that they can be undone at system restart. It also logs all active insert
operations for each fragment at the start of a local checkpoint.
Reads and updates set lock bits and update a header in the hash index entry. These changes are
handled by the page-writing algorithm to ensure that these operations need no UNDO logging.
This buffer is 2MB by default. The minimum value is 1MB, which is sufficient for most applications.
For applications doing extremely large or numerous inserts and deletes together with large
transactions and large primary keys, it may be necessary to increase the size of this buffer. If this
buffer is too small, the NDB storage engine issues internal error code 677 (
Index UNDO buffers
overloaded
).
Important
It is not safe to decrease the value of this parameter during a rolling restart.
•
UndoDataBuffer
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
unsigned
16M
1M - 4G
Restart Type: N
This parameter sets the size of the UNDO data buffer, which performs a function similar to that of
the UNDO index buffer, except the UNDO data buffer is used with regard to data memory rather
than index memory. This buffer is used during the local checkpoint phase of a fragment for inserts,
deletes, and updates.
Because UNDO log entries tend to grow larger as more operations are logged, this buffer is also
larger than its index memory counterpart, with a default value of 16MB.
This amount of memory may be unnecessarily large for some applications. In such cases, it is
possible to decrease this size to a minimum of 1MB.
It is rarely necessary to increase the size of this buffer. If there is such a need, it is a good idea to
check whether the disks can actually handle the load caused by database update activity. A lack of
sufficient disk space cannot be overcome by increasing the size of this buffer.
If this buffer is too small and gets congested, the NDB storage engine issues internal error code 891
(
Data UNDO buffers overloaded
).
Important
It is not safe to decrease the value of this parameter during a rolling restart.
•
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...
