Reads a redo log file, checking it for errors, printing its contents in a human-readable format, or both. ndbd_redo_log_reader is intended for use primarily by MySQL developers and support personnel in debugging and diagnosing problems.
This utility was made available as part of default builds beginning with MySQL Cluster NDB 6.1.3. It remains under development, and its syntax and behavior are subject to change in future releases. For this reason, it should be considered experimental at this time.
The C++ source files for
ndbd_redo_log_reader can be found in the
directory
/storage/ndb/src/kernel/blocks/dblqh/redoLogReader
.
The following table includes options that are specific to the MySQL Cluster program ndbd_redo_log_reader. Additional descriptions follow the table. For options common to all MySQL Cluster programs, see Section 17.4.23, “Options Common to MySQL Cluster Programs”.
Table 17.13. ndbd_redo_log_reader Command Line Options
Format | Description | Introduction | Deprecated | Removed |
---|---|---|---|---|
-nocheck | Do not check records for errors | |||
-noprint | Do not print records |
Usage:
ndbd_redo_log_readerfile_name
[options
]
file_name
is the name of a cluster
REDO log file. REDO log files are located in the numbered
directories under the data node's data directory
(DataDir
); the path under this directory to
the REDO log files matches the pattern
ndb_
.
In each case, the #
_fs/D#
/LCP/#
/T#
F#
.Data#
represents a
number (not necessarily the same number). For more
information, see
Cluster Data Node FileSystemDir
Files.
The name of the file to be read may be followed by one or more of the options listed here:
Like ndb_print_backup_file and
ndb_print_schema_file (and unlike most of
the NDB
utilities that are
intended to be run on a management server host or to connect
to a management server)
ndbd_redo_log_reader must be run on a
cluster data node, since it accesses the data node file system
directly. Because it does not make use of the management
server, this utility can be used when the management server is
not running, and even when the cluster has been completely
shut down.
User Comments
Add your own comment.